From the pile to a draft journal in BTMS.
BTMS is not cloud-hosted, so Pileform posts through a small connector installed on the same network as your BTMS server. The connection is outbound-only, nothing opens in your firewall, and confirmed entries arrive in BTMS as draft journals for a final look before they are finalised there.
Connect once, review, post.
Pileform feeds BTMS. It does not replace it, and a draft in BTMS is still yours to finalise.
Install the connector.
A small on-premise connector on the machine that can see your BTMS server, installed with you in one scheduled remote session. It self-updates, so there is no patching to keep up with.
Drop the pile.
Receipts, invoices and bank statements are read, VAT computed per line, and each line categorised against the chart of accounts and creditor list you already use in BTMS.
Confirm the entries.
Confirm, edit or reject each proposed entry. Inferred fields are flagged so you know exactly what to check.
Post to BTMS as drafts.
Confirmed entries reach BTMS as coded journal entries, using your bank, purchase and sales codes, in draft. Posting is idempotent, so a retried batch never lands twice.
Draft journals, finalised in BTMS.
Entries arrive inside BTMS as drafts, so a final check happens where your books live. Bank-statement transactions post the same way, as double entry.
Outbound-only, on your network.
The connector only ever calls out. There is no inbound port, nothing to open in the firewall, and no cloud copy of BTMS to keep in step.
It learns your coding.
Each supplier’s aliases and default codes are remembered per company, so repeat suppliers code themselves and the review queue gets faster as you confirm.
No lock-in.
You always keep the Excel workbook with the receipt embedded as proof, and a CSV export is one click away. Posting is a convenience, not a cage.
BTMS in Cyprus, with the VAT already decided.
BTMS is a Cyprus ledger, and the pile that reaches it is a Cyprus pile: supplier invoices at 19%, 9%, 5%, 3% and 0% on the same drop, EU supplier invoices under reverse charge, a till receipt that mixes rates on one slip. Pileform decides the rate on every line before anything reaches BTMS, and flags the lines it cannot reconcile instead of guessing.
Reverse charge is detected from the wording on the invoice (Article 196 of the VAT Directive and its Greek and other-language equivalents), cash rounding at the till lands in its own Adjustment column so the workbook always agrees with the printed total, and the source document stays embedded next to its rows for the inspector.
Greek-language invoices are read natively and their line descriptions stay in Greek, which is what the inspector and the BTMS entry both need. One login covers several companies, each with its own BTMS connection.
Posting to BTMS.
Confirmed entries land as coded journal entries, using your bank, purchase and sales codes, in draft. A final check happens inside BTMS before they are finalised there. Bank-statement transactions post the same way, as double entry.
No. The connector on your network only ever calls out. There is no inbound connection and no port to open.
Pileform installs it with you in a single scheduled remote session. Bring someone with access to the machine that runs or can reach BTMS; the connector install, the chart-of-accounts and creditor mapping, and a first attended posting all happen in that session. The connector self-updates afterwards.
Always. Posting to BTMS is optional, layered on top of the workbook you already get. The receipt stays embedded in the file as proof, and you are never locked in: take the Excel or the CSV any time.
Yes. Every line is assigned one of the Cyprus rates (19%, 9%, 5%, 3% or 0%) from what is printed on the document, or flagged for review when the rate is not printed. Reverse charge on EU and other foreign supplier invoices is detected from the invoice wording. The rate reaches BTMS with the draft journal you confirm.
Yes. Each company has its own connection, its own chart of accounts and creditor mapping, its own counterparty memory and its own review queue. Only the owner role can post, whichever company is selected.