EInvoice — data reference

All 17 fields BSuit stores for EInvoice (Finance & Accounting), with the record types they refer to.

On this page

#About EInvoice

EInvoice is a record type in the Finance & Accounting area of BSuit. This page lists everything BSuit stores for each einvoice — 17 fields. No dedicated page for it was found in the menu; records may be created by other screens, imports or automatic processes.

#Fields

Every field stored for a einvoice. “Stored as” is the technical field name, useful when talking to support or building reports. 2 fields are references to other record types.

Fields stored for EInvoice
FieldStored asTypeRequiredMax lengthRefers to
Transaction IdTransactionIdTextNo—Transaction
Provider KeyProviderKeyTextNo——
StatusStatusTextNo——
Clearance ReferenceClearanceReferenceTextNo——
Qr PayloadQrPayloadTextNo——
Signed DocumentSignedDocumentTextNo——
Invoice HashInvoiceHashTextNo——
Submitted AtSubmittedAtDate and timeNo——
Cleared AtClearedAtDate and timeNo——
Cancelled AtCancelledAtDate and timeNo——
Last MessageLastMessageTextNo——
Attempt CountAttemptCountWhole numberNo——
Company IdCompanyIdTextNo—Company
IdIdTextNo——
Created AtCreatedAtDate and timeNo——
Updated AtUpdatedAtDate and timeNo——
Is DeletedIsDeletedYes / NoNo——

#Who can do this

Super Admin and other superuser accounts can always see and do everything, regardless of this list. For everyone else, these are the standard roles that have been granted a permission here in this system’s current setup — an organisation can add, remove or customise roles and their permissions, so treat this as an example, not a guarantee.

Roles with a permission on finance.einvoice, as seeded (2026-09-22)
RoleCreateEditView
Finance ManagerYesYesYes

#Where EInvoice is referenced

Other record types point to this one, so changing or removing a record here can affect them:

Record types that refer to EInvoice
Record typeField
EInvoiceSubmissionLogE Invoice Id

#About this guide

Generated from BSuit’s data model on the date shown under “Seen on a running system”. Field names, types and lengths come from the model itself. References are inferred from field names (a field called “Ledger Id” is treated as pointing to Ledger); the model does not declare relationships, so an inferred link can occasionally be wrong or missing.

About this guide

Status
Partially reviewed
Application
BSuit ERP
Audience
Administrators, analysts and support staff
Owner
BSuit documentation team
Reviewer
Not yet reviewed
Last verified
Never
Checked against
Generated from source revision a36c7a086 on 2026-10-02
Seen on a running system
Not yet
Help version
2026.0.0-preview
Guide ID
erp:data/finance.einvoice
Need more help?If feedback above cannot be sent, email support and quote guide ID erp:data/finance.einvoice.
Email support