Accounting & e-invoicing Books that close themselves.

A real double-entry ledger, built into operations. Bookings, trips, payments, deposits, cancellations, vendors and drivers post journals automatically — once, in the same transaction. Country e-invoicing built in.

Operations in. Journals out.

Operational eventPosts automatically
Booking confirmedJournal posted in the same transaction as the confirmation
Trip completedRevenue and output VAT recognised
Cash tripPosted to driver cash-in-hand until handed in
Agent deposit receivedDeposit recorded · available credit updated
CancellationFee per time-slab policy · reversal posted
Vendor vehicle on tripVendor cost per trip → vendor payable

Balanced by the database

Debit equals credit is enforced at the database level, not just in the app.

Immutable journals

Posted journals are never edited — corrected only by reversal.

Periods close in order

Reopened only by approval; year-end close to retained earnings.

Maker-checker journals

Manual journals are created and reversed by two people.

Drill down to the source

Trial balance and account ledger link back to the originating booking.

Gap-less numbering

Document numbers per company and per year, with no gaps.

Compliant from the first invoice.

E-invoicing built in-house — onboarding per company, clearance and reporting with the tax authority, with a queue and retries. Running in Saudi Arabia? See ZATCA Phase 2.

  1. 01UBL 2.1 XMLEvery invoice, credit and debit note.
  2. 02Hash chainEach invoice chained to the previous.
  3. 03Signature & QRCryptographically signed with QR.
  4. 04Clear or reportCleared or reported to the tax authority, with retries.
  5. 05PDF/A-3Bilingual, cleared XML embedded.

Bank reconciliation Import the statement. Match. Close the month.

  • CSV statement import with saved mappings
  • Duplicate-safe re-import
  • Automatic and manual matching
  • Monthly reconciliation
  • Cash counts with approved over and short amounts

VAT / GST engine

Tax%
  • Rates and rules from the country pack
  • Inclusive or exclusive of price
  • Tax point: earliest of payment or supply
  • Input tax on purchases
  • Tax return compared with the ledger — screen and CSV
FAQ

Frequently asked questions.

How does accounting work in TransferArc?

Every operational event posts its own journal. Confirming a booking, completing a trip, receiving an agent deposit, a cash trip, a cancellation or a vendor vehicle on a trip each create a balanced double-entry journal once, in the same transaction. Nobody re-keys operations into the books.

Does TransferArc support e-invoicing?

Yes. E-invoicing is built in-house. Every invoice, credit note and debit note is produced as UBL 2.1 XML with a hash chain, a cryptographic signature and a QR code, then cleared or reported to the tax authority where the country requires it. The invoice PDF is a bilingual PDF/A-3 with the cleared XML embedded.

Can I reconcile bank statements in TransferArc?

Yes. Import the bank statement as CSV with saved mappings, let TransferArc match transactions automatically and match the rest by hand. Importing the same statement again does not create duplicates. Reconciliation runs monthly, and cash counts record approved over and short amounts.

How does TransferArc handle VAT or GST?

Tax rates and rules come from the country pack. Prices can be inclusive or exclusive of tax, the tax point is the earlier of payment or supply, and input tax on purchases is recorded. The tax return is compared with the ledger, on screen and as CSV.

Can a posted journal be edited?

No. Posted journals are immutable and are corrected only by reversal. Debit equals credit is enforced at the database level, manual journals are created and reversed by two people, and fiscal periods close in order and reopen only by approval.