Picking accounts payable software without breaking the close

Accounts payable software looks like a purchase decision. A bookkeeper sees it as a chart-of-accounts decision. Whatever tool a business picks, its posting logic lands in the general ledger, and the month-end close inherits the result. We have repaired enough ledgers after a sync to know the order matters: settle the accounting questions first, then let the software enforce them.

Settle the process before the software

Map the full path of a bill before anyone signs a contract. Who receives it, who approves it, what evidence attaches, when it is paid, and how the payment is matched. The software should enforce that workflow, not invent it.

A business without an approval policy will not find one inside the tool. The tool will simply record whatever is entered. The same goes for the chart of accounts: if the business cannot decide where postage and bank fees go, the software will decide for you, and the trial balance will show it.

Ask what the tool actually posts

Two posting models matter. Some tools write a summary line to the accounts payable control and to expense at period end. Others post every bill line as it is entered. Each model has its place, but you need to know which one is in front of you.

The test questions are practical. Can the expense account be set per line on the bill? Does that account survive the trip into the ledger? Can you drill from the control balance back to the scanned invoice? If the last answer is no, the reconciliation becomes guesswork.

Protect cut-off and accruals

Here is the test that catches most tools. A bill is dated 29 June and entered on 3 July. If the software posts on the entry date, the expense lands in July, and June's books miss the cost entirely. The close understates June's expenses, and the error surfaces only when someone compares the bill date with the posting date.

A good tool keeps the invoice date, holds unapproved bills out of the ledger, and can list those bills at period end. That list is the raw material for the accrual entry. If the tool does none of this, the accrual is yours to post by hand. If the business uses purchase orders, ask how goods received but not yet invoiced are handled. If the answer is "they are not", that accrual is yours as well.

Watch how payments reach the bank reconciliation

Payment matching follows two mechanics. Some tools mark a bill paid the moment someone clicks a button. Others wait for the bank feed to clear the transaction. The first creates a gap between the accounts payable aging and the bank balance: the aging says paid, the bank says not yet.

Your question is simple. Can the tool produce a clean list of approved but unpaid bills, and another of paid but not yet cleared? Without those two lists, the reconciliation carries timing differences that no one can explain at month end.

Preserve the history before the switch

The migration is where most damage happens. The temptation is to carry only open balances into the new tool and leave the history behind. That loses the audit trail.

Before the switch, export the full vendor list with terms and tax reporting details, the complete bill and payment history, and any deposits or credits. Reconcile the old system's accounts payable balance to the new one before the first day. If the export is missing history, or the totals will not tie, stop. This is no longer data entry. It is a data migration, and it should go to our data migration service while the original file is still intact.

Tell a sync fault from a posting mistake

When the software feeds QuickBooks Online, faults have a signature. Bills appear twice after a sync. Expense accounts silently reset to a default. An opening balance shifts when a re-sync touches an earlier period. The entries look ordinary, which is why they are easy to fix by hand and easy to get wrong.

A posting mistake stays in one place. A sync fault spreads. If you can see repeats or resets across periods, stop re-entering and preserve what you have: the source export, the affected period, and the original file. At that point it stops being bookkeeping and becomes a repair job. Send it to our QuickBooks data repair service before the file is edited further.