How does Vergo's expense management connect to AccountMate?
Through the AccountMate API. Customer-provisioned — the API access sits in your own AccountMate environment: your IT enables it once, and Vergo takes it from there. AccountMate runs on-premise, and its API supports both reading and writing, which is why spend posts into AccountMate rather than arriving as a file somebody has to import. The vendor documents the interface publicly (AccountMate API documentation).
Coding is agreed once, up front. You tell Vergo how card spend should land in AccountMate — which GL accounts, departments and divisions apply to which kinds of purchase — and that mapping is what every posted transaction follows.
What happens to a card charge before it reaches AccountMate?
The work happens at the point of sale, not at month end. A cardholder buys something on a connected card, gets a notification on their phone, photographs the receipt and picks the coding from a list drawn from your own AccountMate setup. If they skip it, Vergo keeps asking until the charge is complete.
Approval happens in Vergo, on the transaction, while the purchase is still fresh in everybody's memory. Nothing reaches AccountMate until it has a receipt, a code and an approver — a different situation from a statement that arrives three weeks later with forty lines and no context.
Policy is checked as each charge lands rather than argued about at month end. Approval rules run per transaction, per merchant category and per person, so a purchase outside the rules is flagged the day it happens and there is no out-of-policy line to explain in AccountMate later.
What does it actually post?
A completed transaction: amount, merchant, date, receipt image, the coding your team agreed, and the record of who approved it. Because the AccountMate API supports writing, that record lands in the ledger as a posted entry rather than a draft somebody still has to finish. Vergo reads back from AccountMate as well, which is how the coding options stay current when your accounts or GL accounts, departments and divisions change.
Corrections stay simple. If something was coded wrong it is fixed the way any posting error is fixed in AccountMate — you are not unpicking a proprietary sync or re-importing a file.
What does this change at month-end close?
It removes the card reconciliation queue. The controller's usual job — matching a statement to receipts, chasing the four people who never sent theirs, then keying coded lines into AccountMate — is already done by the time close starts, because it was done by the person who made each purchase.
Reporting also stops lagging. When card spend posts continuously instead of in a monthly batch, the numbers in AccountMate reflect what has actually been committed, so anyone reviewing costs mid-month sees a near-complete picture rather than one missing every card purchase since the last statement.
Who is this for?
Finance teams running AccountMate with real card volume across several people or sites, currently absorbing that volume through manual entry. The gain scales with how many cards are out and how many GL accounts, departments and divisions each charge has to be split across.
Vergo also covers AP automation and reimbursements on the same AccountMate connection, so vendor bills and employee out-of-pocket claims follow the same coding, approval and posting path as card spend.
Does Vergo integrate with AccountMate?
Yes. Vergo connects through the AccountMate API, and coded, approved card spend posts into AccountMate automatically.
Can we control coding before anything posts?
Yes. Cardholders code each charge against your GL accounts, departments and divisions at purchase, an approver signs off in Vergo, and only then does it post into AccountMate.
What does our team have to do to set it up?
Very little. AccountMate's API access lives in your own environment, so your IT team enables it once and Vergo does the rest. On your side it is the usual accounting work: confirm which GL accounts and departments card spend should land in, approve the mapping, and check the first batch before it becomes routine.
Does AccountMate have built-in expense management?
AccountMate is an accounting system — it records the result of spend. It is not built to connect cards, capture receipts in the field or check policy as a purchase happens, which is the part Vergo adds.
