How to automate recurring supplier invoice coding
Start with a reviewed invoice, then reuse the saved treatment for the same supplier and exact line description. Use keyword rules for stable wording in descriptions that change, and review a new purchase before saving its treatment.
What happens when a supplier changes what it sells?
Review the new purchase before saving its treatment. A rule repeats the decision and conditions your team has set.
Separate reading the invoice from assigning an account
A supplier document contains a description and amount. Your books add a ledger account, tax code and perhaps a tracking category. Data capture and account coding are separate operations, even when they happen in one screen.
A capture error might read an amount incorrectly. A coding error might send a correctly captured amount to the wrong account. Review both. Describing account coding as deterministic means that a saved rule repeats under its matching conditions; it does not describe how the document was read.
Three lines from one supplier
Consider these illustrative descriptions from a supplier. The account names below are examples, not accounting advice.
| Description | Method | What to check |
|---|---|---|
| Monthly support | Reuse the coding from the last exported exact match for this supplier. | The service and accounting treatment are still the same. |
| Office rent September 2026 | A configured keyword rule matches “Office rent”. | The varying month should not change the account. |
| Installation at new premises | Review any fallback coding and decide how this new charge belongs in the books. | A familiar supplier does not make every new purchase routine. |
An exact description match is specific. Even one changed character can stop the match. Datamolino remembers the coding from the last exported matching line for that supplier. The line automation guide explains the scope.
Write a condition you can test
Keyword rules support Begins with, Ends with and Contains. A rule can require all its conditions or at least one. For example, a rule can match any of shipping, freight or carriage, then apply the chosen coding.
Prefer a supplier rule when the meaning depends on the supplier. Use a folder rule when the same wording should receive the same treatment across that folder. A broad word such as service may match charges that should be coded differently.
Use Test rules in the Automation panel to check a description before relying on the condition. Test a false match as well as an intended match. The keyword instructions cover the form and the available coding fields.
Understand which decision wins
In the default exclusive mode, keyword rules are checked in priority order and the first match stops further matching. Supplier keyword rules take priority over folder keyword rules. If no keyword rule matches, Datamolino looks for remembered coding from the supplier's past documents, then supplier defaults and folder defaults.
Exclusive keyword rules need both a ledger account and a tax code. Composite mode can combine fields from multiple matching rules, for example one rule providing an account and another providing tracking. A folder administrator enables that mode. It is not available for FreeAgent. Check the mode before interpreting why a line received particular coding.
Bill Split is another choice for a supplier. It creates allocation lines from amounts or percentages and replaces the captured lines, so it does not run together with that supplier's keyword line automation. Use the line-detail guide to decide which method fits.
Maintain rules when the business changes
Assign someone to review changed suppliers, new descriptions and changes to the chart of accounts or tax treatment. When a rule is wrong, correct it and inspect the affected documents. Do not assume editing a current rule rewrites records already exported to the ledger.
A current rule helps explain the chosen condition. It does not by itself establish a historical audit trail of every rule version. Keep the records your team needs to explain material accounting decisions and review the actual exported transaction.
Compare the controls in another product
A tool may use suggestions for one field and saved rules for another. Ask the vendor to demonstrate a recurring description, a changed reference, two matching conditions and a completely new charge. Check how a person overrides the result and what is saved for next time.
For a team with many new suppliers, reviewed suggestions may reduce initial setup work. A team with recurring line-level treatment may prefer maintaining explicit conditions. The useful test is how each handles your exceptions. Our Dext comparison recognises shared rule capabilities and examines the workflow in more detail.
Do other capture tools also have rules?
Yes. Products can combine rules and predictive suggestions. Compare the available controls, priorities and review behavior rather than treating an entire product as prediction-only.
