AutoCount Invoice Matching: How to Clear Your AR Faster

Published: June 2026 · 5 min read

If your firm uses AutoCount Accounting, accounts receivable matching is probably where your team spends the most manual time. A client pays — sometimes by bank transfer, sometimes DuitNow, sometimes TNG — and you need to match that payment back to the right outstanding invoice in AutoCount.

When you're doing this for 10 or 20 clients, it adds up fast.

This guide covers how AR matching works in AutoCount, where the friction is, and how to clear your outstanding invoices faster.

How AR Matching Works in AutoCount

In AutoCount, when a payment comes in, you record it under Accounts Receivable → Customer Payment. You select the customer, enter the payment amount and date, then tick off which invoices the payment covers.

For clients who pay cleanly — one payment, one invoice — this is straightforward. The problem is most Malaysian SME clients don't pay that way:

  • They pay multiple invoices in one transfer
  • They round up or down ("just pay RM5,000 lah")
  • They pay via DuitNow or TNG, which shows up on your bank statement but the client doesn't tell you which invoices it covers
  • Bank charges and forex adjustments create small mismatches

The result: your AR ageing report in AutoCount shows invoices as outstanding even when the money is already in the bank.

The Matching Problem in Practice

Here's what a typical month looks like for an accounting firm managing AR for a client:

  1. Download bank statement (Maybank or CIMB)
  2. Look at each credit transaction — is this a customer payment?
  3. Check AutoCount AR list — which invoices is this for?
  4. Contact the client if unclear — "this RM3,200 on 15 May, which invoice?"
  5. Record the payment in AutoCount and clear the invoices

Steps 3–4 are where time disappears. For active clients with 30–50 invoices per month, reconciling AR can take an entire morning.

Why Bank Statement Extraction Helps

The core problem is that your bank statement and your AutoCount AR list are in different formats, different systems, and don't talk to each other.

When you extract your bank statement into a structured Excel file — with clean columns for date, amount, reference, and description — you can work through it systematically instead of jumping between a PDF and AutoCount.

With extracted bank data, the workflow becomes:

  1. Upload bank statement PDF → get Excel output
  2. Filter credits (money coming in) by amount
  3. Match against AutoCount's outstanding invoices by amount and date
  4. Record matched payments in AutoCount
  5. Flag unmatched items for follow-up

The extraction step turns a PDF you can't filter or sort into a spreadsheet you can work with in minutes.

Handling DuitNow and TNG Payments in AutoCount

This is one of the most common pain points for Malaysian accounting firms right now. Clients increasingly pay via DuitNow QR or TNG eWallet, and these show up on bank statements in ways that aren't always obvious:

  • DuitNow transfers appear as IBFT or DUITNOW credits on Maybank/CIMB statements
  • TNG payments can appear as a batch settlement rather than individual transactions
  • Reference numbers don't always match invoice numbers

When you extract your bank statement, these transactions appear clearly in the spreadsheet with their full descriptions. You can then match them manually or flag them for client confirmation.

Step-by-Step: AR Matching with AutoCount

Step 1: Get your outstanding AR list from AutoCount Go to Accounts Receivable → Customer Outstanding and export to Excel. This gives you all unpaid invoices with amounts and due dates.

Step 2: Extract your bank statement Upload the PDF bank statement to ScanLedge. You get a clean Excel file with all transactions, including DuitNow, TNG, and IBFT payments.

Step 3: Match by amount Open both Excel files side by side. Filter the bank statement for credits. Match credit amounts to outstanding invoice amounts. For partial payments or bundled payments, look at dates and reference numbers.

Step 4: Record in AutoCount For each matched payment, go to Customer Payment in AutoCount and clear the relevant invoices. Note the bank statement reference in the remarks field for audit trail.

Step 5: Flag unmatched items Any credit on the bank statement that doesn't match an outstanding invoice gets flagged for client follow-up. Any invoice still outstanding after the statement period goes onto your collections list.

Common AutoCount AR Matching Issues

Problem: Payment amount doesn't match any invoice Client paid a round number or deducted something. Check if it covers multiple invoices combined, or look for a matching invoice ± small amounts.

Problem: Can't identify which customer made the payment DuitNow and TNG references are often phone numbers or random strings. If the amount matches an outstanding invoice exactly, that's usually enough. Otherwise, contact the client.

Problem: Invoice already marked paid but bank doesn't show it Client sent a cheque or made an offline payment you recorded but the bank hasn't processed yet. This shows in bank reconciliation, not AR — track it there.

Save 20+ Hours Per Month on AR

For a firm managing AR for 10 clients, automated bank statement extraction typically saves 2–3 hours per client per month — 20–30 hours total.

That's time you're currently spending reading PDFs and manually cross-referencing numbers. With extracted data in Excel, matching becomes mechanical and fast.

ScanLedge extracts Malaysian bank statements — Maybank, CIMB, Public Bank, RHB, and others — into clean Excel files ready for AutoCount AR matching. Handles DuitNow and TNG transactions automatically.

7-day free trial. No credit card needed.

Start your free trial →