Assisted transaction review
Bank statement import for event bookkeeping
Retyping a card statement is the single most avoidable evening in an event director's year.
How directors handle this today
The card statement is where the truth is. It is also where nothing is labelled. A line reading a hardware store, a supermarket and a fuel stop tells you money moved and nothing about which event it moved for.
Most directors deal with this by retyping — working down a statement, deciding what each row was, and entering it somewhere. It is slow, it happens months after the fact when memory is worst, and it produces exactly the duplicate entries and misattributions that make the final figures untrustworthy. The alternative, ignoring the statement and relying on receipts alone, guarantees missed costs.
How it works in Sport Margin
Statement rows enter a review workflow. Nothing becomes a record until it has been approved.
Import rather than retype
Bring bank and credit-card statement rows in directly instead of retyping each transaction. The statement is the source; the work is classification, not data entry.
Assisted categorization and merchant rules
Suggested categorization proposes a treatment for each row, and merchant rules apply consistent handling to vendors that recur — which, in an event business, is most of them. The same supplier gets the same treatment every time without a decision being made afresh.
Duplicate checks and an explicit approval step
Duplicate checks catch rows already recorded from a receipt or entered manually. Nothing joins business expense records until it is approved. The approval step is deliberate: assisted categorization is a suggestion, and the director remains the one deciding what a cost actually was.
What it produces at the end of the year
A cost position built from the statement rather than from recollection, with each row reviewed rather than assumed. Because duplicates are caught at import and receipts attach to the same expense records, the statement, the receipts and the accounts describe the same reality.
Note: this is a statement import workflow, not a live bank feed. You supply the statement file; Sport Margin handles the review and categorization.
Worked example
Illustrative figures from a sample event. Not a customer result.
The sample event's $5,189.22 of other operating costs is the line most likely to arrive via card statement — supplies, signage, refreshments, equipment. Imported, categorised, duplicate-checked against receipts already attached, and approved into the event's expense records, so the event result of $13,974.00 reflects everything actually spent.
What this does not do
This is not a live bank feed. You supply the statement file; Sport Margin does not hold credentials for, or maintain a connection to, your bank. For a business of this size that is a reasonable trade — one import a month covers it, and there is one fewer credential in circulation.
Nothing posts automatically. Assisted categorization proposes a treatment and merchant rules apply consistent handling, but an approval step stands between every suggestion and the record it becomes. The software narrows the decision; it does not make it.
Related event finance features
Connect statement imports with expense tracking, receipt capture, and CSV export.
