Back to the subscription dictionary

Automated bookkeeping

Automated bookkeeping is the use of software to record, categorise, and reconcile financial transactions with minimal human input. It replaces manual data entry with algorithms that connect directly to bank accounts, payment systems, and accounting ledgers, reducing repeated data entry. Correct configuration, exception handling and reconciliation remain essential.

Prepared with AIContent updated

Which steps can be automated?

Automated bookkeeping can include document import, suggested account coding, journal preparation, approved posting and matching against bank data. Products and integrations support different steps. Distinguish a suggestion, a posted entry and a reconciled balance.

Set rules with clear conditions, such as supplier, document type and tax code. Unusual items, missing data and uncertain matches need a visible queue for review.

From invoice to reconciled payment

Illustrative workflow; each step needs appropriate support and review.

  1. Invoice

    Review document, date, accounts and tax

  2. Transfer

    Monitor waiting, error or posted status

  3. Payment

    Settle the relevant receivable, not a new sale

  4. Reconciliation

    Investigate differences and document corrections

This is not a guarantee of any specific integration’s features. Revenue recognition is a separate workflow.

Do not count a sale and its payment twice

If an invoice has already recorded revenue and a receivable, its payment can settle that receivable. It should not automatically create another sale. Fees, part-payments, refunds and chargebacks can need separate entries and references.

Software can process only the events its connection receives and supports. Check delays, retries, duplicates and disconnected accounts. Automatic transfer does not mean immediate or complete recording.

Configuration and reconciliation

Establish account mappings, tax treatment, document numbers, product relations, dates and approval responsibilities. Test a limited set containing an ordinary invoice, credit note, part-payment and expected error. Check the result in both systems before increasing volume.

Monitor errors and reconcile relevant balances against documents, receivables and statements. Retain a change trail and review rules when products, tax requirements or integrations change.

Recognition depends on the connection

Alunta’s current accounting-integration guide distinguishes invoice transfer from revenue recognition. With the required configuration, module and accounts, e-conomic can receive native accrual dates; its monthly accrual run takes place in e-conomic.

Dinero and Billy do not receive native accrual dates. Alunta instead offers its own engine under Settings → Revenue recognition. The first monthly allocation needing posting requires approval after month-end, even when automation is selected. Check the current guide and connection status.

MRR and ARR use different source data

Accounting automation can supply control and cost information. MRR and ARR still use eligible subscriptions and the chosen measurement policy. A failed payment is not automatically churn, and an annual receipt is not one month’s MRR.

Questions and answers

Is importing data the same as posting it?

No. Import may only load documents or create suggestions. Check whether approval, posting and reconciliation are included in the actual workflow.

Can automation record a sale twice?

Yes, for example if both the invoice and its bank receipt are incorrectly coded as a new sale. Use references, duplicate controls and reconciliation to review the whole process.

Are all errors and refunds handled automatically?

Only if the event and its treatment are supported. Check status, evidence and the result in both systems, and review exceptions separately.

Can tax treatment be left entirely to rules?

No. Tax codes and source data must match the actual supply and relevant jurisdiction. Review changes and special cases; automation does not itself determine the correct tax treatment.

Can Alunta recognise revenue with Dinero and Billy?

The current integration guide describes Alunta’s own recognition engine for these products, which do not receive native accrual dates. The first relevant monthly posting needs approval after month-end. This differs from e-conomic’s native accrual workflow.

Sources and documentation

We update our content regularly and do our best to keep it accurate. If you find an error or think something is missing, please tell us. We are always looking for ways to improve the content.

Found an error? Let us know