Your Accountant Is the Weekly User, Not a Month-End Recipient
If the only time your accountant sees Plandesk is a CSV in April, you still have two systems. Here is the role, the exports, and the permissions that keep the books on the same invoices you issued.
Your Accountant Is the Weekly User, Not a Month-End Recipient
US bank-partner pages sell a console to the relationship manager, so the client opens the product every day. For a European shop or restaurant, that person is not a banker. It is the Steuerberater, the gestoría, the biuro rachunkowe.
They already see your VAT. They already sign or file. If they still wait for a dropbox of PDFs, every e-invoice mandate you just survived will be re-typed into their suite. That is how DATEV, A3, and JPK_V7 diverge from the till.
What They Need That a Portal Does Not
US partner programs offer an "advisor console" so the bank can comment on spend. Your accountant needs something narrower and more legal:
| Market | What they file from | What they must be able to pull without you |
|---|---|---|
| Germany | DATEV, DATEV-CSV, DSFinV-K, GoBD archive of the structured e-invoice | TSE/DSFinV-K export, XRechnung/ZUGFeRD originals, not flattened PDFs |
| Spain | A3, Holded, the AEAT copies, Verifactu chain | SIF records, QR-bearing visualisations, Crea y Crece status when live |
| Poland | JPK_V7, KSeF session, UPO | Entity-level KSeF access (grant by NIP, dalsze przekazywanie, never permissions-management) |
A login with "accountant" as a role beats a ZIP. They can see invoices, aging, and the export. They cannot change IBAN master data, fire a staff member, or grant KSeF rights to a third firm.
Article 13 covers the Polish grant procedure. Repeat the same idea everywhere: access is per legal entity, revocable, logged.
Weekly, Not April
OSS returns, JPK, Verifactu event logs, and German receive-side e-invoices do not wait for year end. A weekly pull:
- New sales invoices and credit notes
- Incoming supplier e-invoices (Germany: you must be able to receive them since 1 January 2025)
- Payments matched and unmatched
- Hash-chain or KSeF errors that would otherwise sit until the inspector asks
If that pull is a person emailing "the Excel from the till," you will miss a KSeF rejection, a BT-10 bounce, or a Verifactu incident mode you never closed.
Dual Control Beats "Full Access"
The accountant who can issue and the owner who can pay is a healthy split. The accountant who can also rewrite the payee IBAN is how substitution fraud lands. Keep:
- Issue / read / export for the firm
- Pay / change payment means / grant permissions for the owner or a named internal admin
- One entity per grant. A JDG and a GmbH are not one client in the tax system even if they share a kitchen
Do not copy bank "white-glove onboarding" language onto this. A gestoría does not need a co-branded PDF. They need a file A3 will ingest on Monday.
What This Is Not
It is not a referral portal for banks. It is not a spend dashboard so a relationship manager can upsell a card. It is not "invite your advisor and we will email them marketing."
It is a role on the same invoices, tickets, and stock movements the operator already produces. DATEV and A3 are named because that is what those firms open. JPK and KSeF are named because Poland does not let you skip the state node.
Plandesk ships that role and those exports. The accountant who logs in weekly is how the books stay on the legal artefact (FA(3), XRechnung, signed Facturae), not on a reconstructed PDF.
This material is information of a general nature and does not constitute legal or tax advice. For a specific situation, verify the current rules or consult a qualified adviser.