Sage 50 export
Turn the receipts and invoices on an engagement into a spreadsheet of transactions you can bring into Sage 50. A file, not a live connection.
Sage 50 works differently from the other two. There is no account to connect and nothing syncs — Vylan produces a file, and you take it to Sage.
That is worth saying plainly because it changes how you use it: nothing happens on its own, and nothing in Sage changes until you import the file yourself.
Producing the file
- Open Integrations and choose Sage 50.
- Export an engagement, then Choose an engagement.
- Vylan reads through what is attached — Checking documents… — and shows you what it found.
- Download CSV.
Read the preview before you download
The preview is the point of the screen, not a formality. It has two lists worth your attention.
- Skipped — documents left out, with the reason. Statements list many transactions, not one entry. and Not a receipt or invoice. are the usual two.
- Check these before you trust them — read, but with something the extraction was unsure about.
That second list is a help, not a guarantee. A figure can be read wrongly without being flagged, so the export is a first draft of your data entry rather than a finished ledger.
What is in the file, and what is not
Each row is a transaction read off a document: the supplier, the date, the amounts and the taxes it could identify. It does not choose your accounts. Which expense account a bill belongs in is a judgement about that client's books, and it stays yours — you map it as you import.
Only what Vylan has read gets exported, so a document nothing ever looked at will not be in the file. And it is one engagement per export — there is no whole-firm button.
If you get Nothing to export yet, it usually means the documents on that engagement are not receipts or invoices, rather than that anything is broken.