Skip to content

A ledger-ready accounting export.

The accounting route out of MetlSys is a file, not a connection. A posting run turns a period of invoices, credit notes and matched supplier invoices into a ledger-ready CSV, covering the sales and purchase ledgers, and you import that file into your accounting package. It is an export you run, not a live sync, and that belongs at the top of the page.

One file, both ledgers.

Sales ledger

POSTING RUN CSV

Purchase ledger

POSTING RUN CSV

Your accounting package is another company’s product. MetlSys is not a partner, reseller or certified app of any accounting package, and nothing on this page is endorsed by one.

What the file carries and never does.

Two lists, because the second is the half most software companies leave out.

What the file carries

  • Sales invoices and credit notes raised in MetlSys, carrying the VAT code held against the customer rather than a house default.
  • The purchase side from supplier invoice matching, so what you agreed on the order, what arrived at the door and what the supplier billed have already been reconciled before they reach the ledger.
  • Foreign-currency entries at the rate MetlSys recorded on the day, where multi-currency is switched on.
  • The MetlSys invoice number on every line, so a query in the accounts package walks back to the despatch, the order, the batch and the heat number behind it.

What it does not do

  • It does not write into your accounting system. Nothing is created there on your behalf, and nothing is amended or removed there either.
  • Nothing comes back the other way. Journals, nominal postings and reconciliations you do in the accounts package stay in the accounts package; MetlSys does not read them.
  • There is no live balance mirror. Aged debt, credit exposure and the reminder ladder in MetlSys are worked out from MetlSys invoices and receipts, not from your ledger.
  • There is no vendor connector to authorise, renew or watch for breakage. The file is the whole interface, which is the point.
  • It does not replace your accounting package. MetlSys runs the operation and raises the paperwork; the nominal ledger, the VAT return and the statutory accounts stay where they are.

The finance module that produces those entries, from invoicing off a clean proof of delivery through to aged debt and the reminder ladder, is set out in full on the features page, finance module. The export itself sits on the Corporate tier, with pricing page listing what each tier switches on.

Why a file

A live sync reads better. An export fails better.

Two-way connectors go wrong quietly. A token expires, a vendor changes an endpoint, a mapping drifts, and a fortnight of invoices queues up where nobody is watching until month end goes looking. A file has none of those failure points.

It also puts a person in the loop on purpose. You run the posting run, look at what is in it, and import it. You keep the file, so the handover between the operation and the ledger is something you can point at during an audit, not a background job you take on trust. If that judgement changes, this page changes with it.

Where else data crosses the boundary.

Everything here is live in the product today. Where a route is a genuine two-way connection, it says so.

Card and Bacs payments

Pay-now links on invoices, reminders and the customer portal settle into your own Stripe account. Card on smaller invoices, Bacs Direct Debit on larger ones, and refunds that start from a credit note so nothing gets paid back twice. Taking money has to happen live, so this one does.

EDI trading partners

EDIFACT and X12 for the customers who work that way. Inbound purchase orders land as draft sales orders; order responses, despatch advices and invoices go back out. Every message is logged, with a retry when one bounces. Unlike the accounting route, this genuinely is a two-way exchange.

API access

The Corporate tier includes API access for firms with their own developers, alongside custom work scoped and priced before a line is written. If you need something wired to a system we have never seen, that is the door.

Document storage

Mill test certificates, delivery notes and cert packs live in platform object storage, with the database itself in London. Customers collect bundles on short-lived secure links from the portal instead of chasing your office for another copy.

AI document reading

Mill test certificates, delivery notes, customer purchase orders and supplier confirmations are read into drafts by Anthropic’s Claude models. The draft waits for a person. Nothing is written to your data without an explicit confirmation.

Email and anti-spam

Order acknowledgements, certificate packs, statements and payment reminders are sent through Resend. On this website, the contact form is checked by Cloudflare Turnstile, a privacy-first challenge that sets no tracking cookie.

See AI and automation

Common questions

The three we get asked every time.

What does the accounting export produce?

A posting run produces a ledger-ready CSV covering the sales and purchase ledgers, which you then import into your accounting package. It is an export you run, not a live two-way sync.

Do we still need an accounting package?

Yes. MetlSys runs the stockholding operation and raises the invoices and credit notes; the accounting export hands those entries over. The nominal ledger, VAT returns and statutory accounts remain the job of your accounting package.

Which MetlSys tier includes the accounting export?

The Corporate tier, alongside multi-currency, credit control, the customer portal, fleet and transport, EDI and API access. Lite and Professional cover the operational side without the accounting export.

Tier contents, traceability, migration from a legacy system and where your data is held are all answered on the frequently asked questions page. If yours is not there, ask it. You get a straight answer or an honest “not yet”.

Bring your accountant to the demo.

We run a posting run on demo data and open the CSV. Your accountant says whether it lands cleanly in the ledger you use.