By KYN AI Advisory Team — AI implementation specialists, Singapore
Bill entry has three parts: read the document, check it, post it. Software can read and check. A person should confirm the posting. When the reading is automated, the hours spent keying vendor, date, amount and tax go away, and the person's time shifts to exceptions. This article follows one bill from the inbox to the ledger. It is a description of the method and of KYN's own books, not a promise of hours saved: we have not published a client figure and we do not quote one. Measure your own keying time first; the method is below.
What does manual bill entry involve?
For each bill, a person usually does the following:
- Finds the bill in an inbox or a shared folder.
- Opens it and reads vendor, bill number, date, due date, line items, tax and total.
- Checks whether the vendor exists in the ledger and creates it if not.
- Checks the bill is not already entered.
- Picks the expense account and, where relevant, the project or cost centre.
- Keys the entry and attaches the document.
- Routes it for approval and, later, for payment.
Steps 1, 2, 3, 4 and 6 are search and typing. Steps 5 and 7 are judgement and control. Software handles the first group well. The second group is where errors cost money.
How does a bill move through an automated flow?
- Intake. Bills arrive in one mailbox or folder. The system watches it, saves each attachment and records the sender and time.
- Read. A model extracts vendor, bill number, dates, currency, tax and total, plus line items if you need them. Each field carries a confidence flag.
- Match the vendor. The system compares against the vendor list. A new vendor goes to a person.
- Check for duplicates. Same vendor, same number, same amount, or the same document hash, stops the bill and shows the original.
- Check the arithmetic. Lines sum to the subtotal; subtotal plus tax equals the total. A mismatch is flagged, because a misread digit usually shows up here.
- Propose coding. The system suggests the expense account from the vendor's history. A person confirms.
- Queue for review. A draft entry appears with the document beside it. The reviewer confirms, edits or rejects.
- Post and route. Confirmed entries post to the ledger. Payment waits for a named person.
On KYN's own books, bills are read from Gmail into a bills table, and receivables are chased at 3, 14 and 30 days. Each action is logged with the actor.
What are the checks that matter?
Reading is the easy part. Checking is the part that keeps the ledger clean.
| Check | Error it catches | |---|---| | Duplicate on vendor, number, amount | The same bill entered twice | | Document hash | The same file forwarded again | | Arithmetic on lines, tax, total | Misread digits | | Currency against vendor history | A USD bill read as SGD | | Date inside the open period | Postings into a locked month | | Bank details changed from last time | Payment-redirection fraud | | Approval limit by amount | A bill above the person's authority |
The bank-details check deserves a special note. A bill that arrives with new bank details is a common route for payment fraud. The system compares details with the last bill from the same vendor and stops the payment until a named person confirms by another channel.
What does the reviewer actually do?
The reviewer sees a table: document thumbnail, extracted fields, flags, proposed account. They work in three modes.
- Clean bills. All fields confident, no flags, vendor known. Confirm in batches after scanning.
- Flagged bills. One or more checks failed. Fix, then confirm.
- New vendors. Create the vendor and verify details once.
Over time, the clean share rises, because vendor history grows and the coding suggestions improve. The reviewer's time falls on the clean bills and stays on the flagged ones, which is where it should be.
How do you measure the saving honestly?
Time your current process for one month.
- Pick 30 bills across vendors.
- Time each from "opened" to "posted", including look-ups.
- Record the number of bills a week and the share that are repeat vendors.
- Multiply to get monthly hours.
After the build, run the same measure on the review step. The difference is your saving. Include the review time, the exceptions and the monthly retainer in the comparison, or you will overstate it. For a business with a few dozen bills a month, the saving may be small and a simple intake rule may be enough. Our guide to choosing automation versus hiring covers that decision.
What about receipts and claims?
Receipts follow the same shape with one difference: the source of truth is the card statement. See how to scan receipts for GST claims in Singapore and expense-claim reconciliation across SGD and USD cards.
What are the trade-offs?
- Layout variety. Unusual layouts, handwritten bills and poor scans reduce accuracy. They go to manual entry.
- Coding judgement. Suggestions help, but the account choice still rests with a person.
- Duplicate risk during rollout. Running the old and new process together double-enters. Set a clean start date.
When is automation not worth it?
Three cases.
- Low volume. Under a few dozen bills a month, a shared inbox, a checklist and a standing weekly slot in the accountant's diary may be enough.
- Highly irregular documents. If every bill is a different hand-written layout, extraction accuracy stays low and review time stays high.
- Unstable process. If nobody agrees who approves what, fix that first. A system will only record the disagreement faster.
In each case, a review of the process is cheaper than a build, and we say so when the numbers show it.
How do you start without breaking the books?
Set a clean start date, such as the first day of a month. Bills dated before it stay in the old process; bills received after it go through the new intake. Run both for one close only to compare, and compare by count and total: the number of bills and the sum posted should agree. Any difference is a finding, either a missed bill or a duplicate. Keep the original documents linked to each entry so an auditor can open the source from the ledger line in one click.
Where KYN fits
KYN builds bill intake as part of a finance system in a cloud account in your name. Extraction, checks and drafts are automatic; posting and payment wait for a named person. Agents have their own restricted accounts and the database uses row-level security. The first 14 days are a review of your stack and interviews with your team; a full build ships in under 90 days. See pricing.
Frequently asked questions
Can software enter supplier invoices without a person?
It can read, check and draft them. Posting and payment should be confirmed by a named person, because a wrong entry or a changed bank account costs money.
How accurate is automated invoice reading?
It varies by layout and scan quality, so measure it on 100 or more of your own bills before launch. Arithmetic checks catch most misread amounts.
How do I stop duplicate bills?
Check vendor, bill number and amount, and also hash the file. Either match stops the bill and shows the original for a person to review.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
