Accounts payable automation

Every line coded, with the reason written out

Coding is decided in order of confidence, and the page tells you which level the answer came from. First, anything you have confirmed before for that supplier — once you have told SyncWise how a supplier's lines are coded, it does not ask again. Failing that, how the line has been coded in your own ledger historically, which needs a consistent run of previous bills before it counts. Failing that, SyncWise proposes a code from what the line actually says.

That last case is treated differently on purpose. A proposed code that no human has confirmed will not let the bill be approved — SyncWise blocks it until someone says yes or corrects it. When it corrects, it remembers, and the same line does not come back a second time. The reason for each line is written in plain English next to it, so a reviewer can agree or disagree in a second rather than opening the ledger to work out what happened.

Matched to your purchase orders

Where you raise purchase orders, bills are matched against them: the supplier, the lines, the quantities and the amounts. A bill that does not match its order is held with the difference shown, rather than posted and discovered at month end.

This is where over-billing is caught. A supplier invoicing for more than was ordered, or invoicing twice against one order, is visible at the point the bill arrives, which is the only point at which it is cheap to deal with.

The checks that actually stop losses

Four checks run on every supplier bill before it is allowed near your ledger.

The same bill arriving twice

Checked against the bills already in your accounting software, not only against what SyncWise has previously seen. A bill forwarded by two people, or re-sent by the supplier with a new reference, is caught before it becomes a double payment.

A changed bank account

Bank details are compared against every previous bill from that supplier. If they differ, the bill stops and says so. Invoice redirection fraud works precisely because a changed sort code on a familiar-looking bill is invisible to a busy person; it is not invisible to a comparison.

The bill that never arrived

SyncWise learns each supplier's rhythm from your own history. A supplier who normally bills you monthly and has gone quiet is flagged as missing before the period closes, so the accrual is a decision rather than an oversight.

Credit notes traced to the invoice

A credit note is recognised as a credit note and the original invoice it relates to is suggested, with the reasons given. Linking the two is a human action — SyncWise proposes, it does not decide.

Supplier statements reconciled line by line

Send a supplier statement and SyncWise ticks it off against what you have: every invoice line matched to a bill in your ledger or in the queue, every payment line matched to a payment, and the statement's own arithmetic checked. What comes back is what is missing on each side — invoices you have never seen, payments the supplier has not recorded, and anything that does not agree.

It also runs the check in reverse, so a bill sitting in your ledger that the supplier's statement does not mention is surfaced too. The output is a report. Nothing is posted or changed off the back of a statement.

Alerts shaped around how your team works

You decide what deserves a human's attention: which suppliers, which amounts, which kinds of change. An unexpected bill from a supplier who normally invoices for a few hundred pounds is not the same event as a routine one, and it should not arrive in the same way.

Questions people ask about this