Before the first invoice
Prepare the partner through REST, MCP, or Invoicing → Partners. A company admin must then review and activate it in Invoicing → Partners. Activation requires:- registered legal name, Finnish business ID, and postal address;
- the partner’s own IBAN and bookkeeping-copy email;
- signed mandate reference and KYC reference.
PATCH /portal/seller-profiles/{profile_id}. The company admin then verifies that LAC holds the evidence and selects Start using this partner in the portal.
1. Get the seller profile
Use a write-scoped key because the result contains bank and evidence references.status is active. Copy its id to the draft’s seller_profile_id.
2. Resolve the buyer’s e-invoice route
Search by the buyer’s name, Finnish business ID, or FI VAT ID. LAC asks Maventa for the current OVT/e-invoice address and operator; you do not create a receiver record.einvoice_address and operator to the draft’s customer.
3. Create the draft
GET /portal/invoices/{draft_id}. Confirm seller_profile_id, partner legal name, business ID, and IBAN before issue.
Consumer buyers and PDF delivery
For a consumer, use the customer-directoryid returned by LAC when updating
an existing buyer. A Business ID and e-invoice route are not required for the
PDF channel.
POST /portal/invoices/{draft_id}/finalize. The
response includes pdf_document_id, pdf_sha256, pdf_size_bytes, and
pdf_available=true. Download the exact retained bytes from
GET /portal/invoices/{invoice_id}/pdf; its ETag and X-Content-SHA256
headers equal pdf_sha256. LAC keeps that immutable PDF as accounting evidence.
You can attach the downloaded PDF to your own email, or host it behind your own
authenticated link and send that link by text message. Finalizing does not send
anything to the consumer.
A consumer e-invoice still requires the consumer to have activated e-invoicing
with their bank and supplied the corresponding receiving route. The PDF flow
does not require that subscription.
4. Send
/request-approval first and wait for a person to approve it in the portal.
The send has these fixed effects:
- the Finvoice seller, postal address, business ID, VAT identity, invoice series, and payment IBAN come from the partner profile;
- the tenant’s Maventa address is the technical material-handler route, not the legal seller;
- the partner receives a PDF copy for its own books;
posts_ledger=false: no tenant journal, output VAT, receivable, aging, or overdue item is created.
MCP
Usecreate_seller_profile and update_seller_profile to prepare the draft partner. A company admin activates it in the portal after checking the evidence. Then use list_seller_profiles, search_invoice_receivers, create_invoice_draft, get_invoice, and send_invoice. MCP uses the same draft and customer fields as REST, but it does not expose the seller-profile status field.
For recovery, use retry_invoice_send only after a safe failure. Use retry_partner_invoice_copy only after you verified that the partner did not receive an ambiguous earlier copy. LAC refuses ambiguous e-invoice sends until the outcome is checked in Maventa.