The most comforting sentence in a cloud file is “the feed is up to date”. It is also how a quarter closes without anyone opening a statement. Rules fire. Circles turn green. GST at 10 per cent is applied to a drawing because the rule said “VISA is meals”. A transfer from the offset to the working account becomes income in one place and a mystery in the other. Merchant settlements land as sales, net of fees, and the P&L congratulates you on a margin you did not earn.
The original Bookkeeping Centre used to collect paper weekly and turn it into a file an outsider could walk. The digital version is the same job. A feed is a messenger. It is not the books. This essay is about the difference, written for the owner who codes on Sunday and the bookkeeper who inherits the login in May.
What a reconciliation still is
A bank reconciliation is a proof that the ledger’s cash agrees with the bank’s closing balance on a named day, after you have explained every uncleared item. The inputs are:
- the statement PDF (or a bank-issued CSV you treat as a statement, not as a feed)
- the ledger’s cash account
- a list of outstanding deposits and unpresented payments you can name
The feed can populate the list of movements. It cannot certify the closing balance. Feeds drop lines. They duplicate lines. They miss a day. They arrive in a different timezone and split a midnight settlement. They do not include the bank’s opening balance the way a statement does when you first convert a file.
In Xero, “ok” on the reconcile screen is not the same as “reconciled to statement”. In MYOB, a matched feed is not the same as a signed bank rec. Do the extra step: statement closing balance equals ledger balance plus or minus the uncleared items you have listed. File the PDF with the month-end pack.
Loans, cards, offsets and clearing-house wallets belong in the same ritual. A file that only reconciles the working account is a file that will discover the card in BAS week.
Rules that hide drawings
Owner drawings are the first thing a bad rule conceals. The owner pays the home insurance, the school, the family holiday, or a personal credit card from the business account. A rule sees a familiar merchant and codes “insurance” or “travel” with GST. The P&L absorbs a private life. The balance sheet never shows a drawing or a loan.
Fix the habit, not only the line:
- create Drawings (sole trader) or Owner / director loan (company) and use those names
- never let a bank rule touch those accounts from a merchant keyword
- review any payment to a person who shares a surname with the owner before you accept a suggested match
- if the company pays a shareholder’s personal card, it is a loan or a deemed issue until someone documents it — not “motor vehicle”
A company that hides drawings in meals will also hide them from a Division 7A conversation. That is not a bookkeeping kindness. It is a July invoice from the tax agent. Keep the related-party mess visible, the way the chart of accounts asks.
Personal deposits go the other way. A director topping up cash is not sales. A rule that codes every inbound transfer as income will invent GST at 10 per cent on money that was already yours. That invented GST will lodge if you do not catch it, and you will pay the ATO for the privilege of lending yourself money.
Transfers that do not net
Transfers between your own accounts must net to zero across the file. Working account to saver. Saver to offset. Offset to loan. Card paid from working. Clearing-house wallet topped up for payday super.
A rule that says “TRANSFER is transfer” and dumps every match into a single suspense account is how you accumulate a $40,000 fog. Name the other side. In Xero, transfer directly between bank accounts. Do not income one and expense the other.
Common transfer failures:
- paying the credit card from the working account and coding the payment as “bank charges”
- sweeping to an offset and leaving the offset unconnected, so the working account looks poorer than the business is
- treating a redraw as income
- treating a loan repayment as an expense for the full amount, instead of splitting principal and interest
- topping up a super clearing-house wallet and expensing it as Super Guarantee, then expensing SG again on payday
If you cannot see both legs on the same day, you are not looking at a transfer. You are looking at a missing account.
Merchant fees, net settlements and the sales lie
Card settlements rarely equal sales. The acquirer pays you sales minus fees, sometimes minus refunds, sometimes plus a batch from yesterday. A rule that codes the deposit as Sales (GST on income) understates income and misses the fee. GST may be wrong on both sides.
The boring method still works:
- record the sales at the invoice or the till, GST at 10 per cent on taxable sales
- record the settlement as a receipt against those invoices, or as a clearing
- record the merchant fee as an expense, with the GST treatment the tax invoice from the acquirer supports
If you cannot get a settlement report, you cannot honestly code the deposit. Ask for the report. It is a source document, not a nice-to-have.
Head-contractor portals and marketplace settlements do the same thing to trades and small retailers. A $20,000 claim that arrives as $19,100 is not a $900 discount unless it is. It may be retention, a portal fee, or a variation you have not invoiced. Do not let a rule write off the difference to “rounding”.
The false close
A false close is a month that looks finished because the feed is empty. The symptoms:
- reconciled badge is green, but nobody has opened a PDF
- uncoded list is empty because everything hit a rule
- GST report has not been compared to the GST control account
- Super payable has not been compared to the clearing house
- aged receivables include invoices the customer has already paid into an account you do not feed
- aged payables exclude the card you do not feed
- stock and WIP have not been touched
- the lock date is still last year, or does not exist
The close in month-end for owner-operators is the antidote: statements first, payroll second, GST third, people who owe you and people you owe, then a two-page pack, then a lock. The feed is an input to step one, not a substitute for the pack.
Software will offer to “auto-reconcile”. Auto-reconcile is a rule engine with a shorter name. Use it only on lines you would be willing to see read aloud at a BAS review.
Writing rules that deserve to live
A good rule is boring:
- one merchant, or a unique reference
- one contact
- one account
- one tax rate you have thought about
- no drawings, no transfers, no loan accounts, no “miscellaneous”
Review rules quarterly. Delete any rule that has fired onto more than one kind of payment. A “COLES” rule that once coded kitchen milk and now codes the owner’s groceries is a rule that has retired without telling you.
Never accept a suggested rule on a Friday afternoon for a line you do not recognise. Park it in “Uncoded — this week” and ask on Monday. Speed is how private school fees become “training”.
If several people code, split duties. The person who creates rules should not be the only person who reviews the exception report. Cloud security is part of this: a departed staff member’s rule will keep firing after their login is gone, if you let it.
GST, the feed, and the BAS you have not yet lodged
Feeds do not know your GST basis. A cash-basis file still needs the tax rate on the invoice or the spend money, not a guess at settlement. An accrual-basis file needs the invoice dated in the right period, even if the feed lands next quarter.
Capital items bought on a card will arrive looking like expenses. Private proportions will arrive looking like full credits. GST-free purchases (basic food, some medical) will arrive with a default of GST at 10 per cent if your account default is lazy. The GST audit report exists because the feed will not apologise.
Before you lodge, the GST control account must equal the draft activity statement. If it does not, the feed is usually where the extra 10 per cent was invented. See the BAS lodgement calendar for the clock, and Xero setup for the settings that prevent the invention.
A weekly feed ritual that is not a close
You can touch the feed every week without pretending the month is closed:
- Match transfers first, both legs.
- Match known supplier bills and customer invoices. Do not create new invoices from the feed unless that is a deliberate cash system.
- Code new spend only when you have a source document or a named question.
- Leave anything you do not recognise uncoded. Do not invent.
- Glance at drawings and related-party names.
- Do not lock. Do not call it a close.
Then, in the first ten days of the month, do the real thing with PDFs.
The Rosebery desk used to say that a bank statement is a letter from someone who does not work for you. A feed is a rumour about that letter. You can use the rumour to get faster. You cannot file the rumour and tell a tax agent the month is closed. They will ask for the letter. They should.
.jpg){kind=link}