One of the quiet time sinks in Thai freelancing is matching the slip a client dropped in LINE to the right invoice and confirming the money actually arrived. With bank screening getting stricter this year, being able to show which payment belongs to which job matters even more. Here is the whole flow in MANA, from setup to the income sitting in your books.
Why verify a slip instead of just looking at it
A convincing fake slip takes two minutes in a photo editor — but honest mistakes are far more common: a client transfers 500 baht short, pays the same invoice twice, or resends last month's slip by accident. Verifying against bank-side data tells you immediately whether that transaction reference is real, the amount matches, and the money went to your account.
Set up three things first
- A wallet for incoming payments. In Finance, create the wallet tied to the bank account or PromptPay ID you actually collect with.
- Show it on invoices. Mark that wallet as visible on documents and set it as the default, so the PromptPay QR appears on every invoice without you picking it each time.
- Double-check the PromptPay ID. Verification compares the slip's receiver against the account number or PromptPay ID on the document. A typo here reads as a mismatch.
Step 1 — Publish the invoice and send the link
Create the invoice as usual, publish it, and send the public link. Your client opens it without signing up and sees a PromptPay QR they can scan straight from their banking app.
Step 2 — The client attaches the slip (or you do)
After paying, the client uploads the slip right on the document page. If they send it to you in LINE out of habit, upload it yourself from the document detail view — same result.
Two limits worth knowing:
- A document holds one pending slip at a time; clear the old one first.
- Guest uploads through the public link are capped at 20 attempts per document over its lifetime, so nobody can burn your quota.
Step 3 — MANA reads and checks it
On upload, MANA extracts the amount, date and currency from the image and compares them to the amount due. When you run the bank-side check, three things happen:
- The QR on the slip is decoded to get the real transaction reference, not just numbers printed on an image.
- The amount is compared to the outstanding balance, with a one-satang tolerance for rounding — not for short payments.
- The receiver is compared to your account number or PromptPay ID. Banks mask part of the account number, so matching runs on the longest unmasked digit sequence.
Pass all three and the slip is marked verified.
When verification fails
Usual causes: a blurry photo where the QR can't be decoded, a cropped screenshot with the QR cut off, an underpayment, or a transfer to an account other than the one on the document.
What to do:
- Ask for the original full-size slip from the banking app and retry.
- If it really was short, have the client send the difference before confirming.
- If the money genuinely arrived but can't be machine-verified — for example a channel whose slip has no QR — you can confirm it yourself, acknowledging it as unverified. MANA records that it was a manual confirmation.
Step 4 — What confirming actually does
Confirming is not just a "paid" badge. MANA will:
- Create a revenue entry in Finance using the slip's amount, currency and date.
- Post it to the wallet you chose, and attach it to the project if the document belongs to one.
- Reconcile that entry against the document automatically, closing the invoice so it stops showing as outstanding.
As a side effect, your project reports and cash-flow forecast update immediately — no second round of data entry anywhere.
Step 5 — Issue the receipt
Once the balance is closed, issue the receipt from that same invoice. Quotation, invoice and receipt stay linked as one chain — the evidence set you need when a client's accounting team asks, when you file tax, and when a bank asks you to explain where an incoming transfer came from.
Verification quota by plan
- Free — no bank-side verification, but you can still attach slips and confirm manually.
- Mana — 30 verifications per month.
- Aether — unlimited.
If you use up a month's quota, remaining slips still record and confirm manually as normal.
Habits that make this flow work
- Send the document link, not a PDF attachment. The link is what lets the client hand the slip back to you.
- One invoice per milestone. Don't combine two milestones and let the client pay in pieces; the amount won't match and verification will fail.
- If 3% withholding applies, the transfer will be less than the document total — put the withholding line on the document from the start so the outstanding balance equals what the client actually sends.
- Keep a dedicated business wallet. When you need to explain where money came from, you want one clean chain to show.
Try it on your next invoice. If it runs end to end — client scans, pays, attaches, you confirm, receipt issued — make it the default for every invoice after that.
