PRODUCT CAPABILITIES
What’s in scope.
01
Linked compliance records
Attach and track relevant documents against core Business Central entities. Linking a record to the customer, supplier, employee or asset gives the team a consistent place to find its supporting information.
02
Expiry monitoring
Record document validity and monitor upcoming expiries. Notifications can support renewal requests and follow-up with the party responsible for supplying an updated document.
03
Evidence for review
Maintain a traceable record of supporting documents and their status. This helps teams assemble information for audits and inspections without treating the presence of a file as proof of compliance.
04
Multiple document types
Manage certification and other statutory or business-required records within the configured scope. The published offer includes support for different certification types and multiple business units.
Define what is required and who owns renewal
The extension supports document tracking; the organisation still determines which records are required and whether they are valid. Braintree can scope the entities, document types and notification process around those responsibilities.
✓
Identify the entities and document categories to be tracked.
✓
Assign responsibility for checking and accepting new documents.
✓
Agree expiry rules, notifications and renewal follow-up.
✓
Confirm compatibility and deployment requirements for the Business Central environment.
THE PRODUCT IN PRACTICE
Track documents by status
The published Compliance Document Administration page groups outstanding, pending and expired documents so users can follow up from the role centre.
Read the workflow guide
01
A register connected to the entity
Compliance Document Tracker records documents against the Business Central entity they concern. The Help guide describes customers, vendors, items, fixed assets, resources and employees, with configurable document associations. An administrator can work from a document-management role centre or open the relevant entity card to see its linked records. This gives the renewal process a business context rather than leaving every file in a separate folder or spreadsheet.
Each entry contains a document type, the associated entity, issue information and the supporting file when it has been received. The configured number series identifies the entry. Document details and attachments belong together, but they serve different purposes: a stored file provides evidence to inspect, while the register shows how the organisation is managing that evidence.
02
Define document types once
The setup guide separates issuing authorities from document types. An authority record can carry its name, a membership or registration reference and a vendor link where relevant to fee payments. A document type can specify its issuing authority, validity formula, jurisdiction description, importance and eligible entity types. Importance can be recorded as optional, recommended or mandatory according to the organisation’s own rules.
Entity defaults provide a suggested collection of documents for new records. For example, a customer onboarding process can use a predefined set of required document categories. Duplicate controls can determine whether more than one edition of a document type may be recorded for an entity. These settings should reflect the real document lifecycle, including whether multiple valid records need to coexist.
03
Separate receipt, approval and renewal
The documented creation process records the issue date and document number, then allows the attachment and status to be updated when the evidence arrives. An authorised person can move a received record to Approved. The setup also provides an approval-workflow template that can be configured and enabled around business rules.
Expiry monitoring depends on the document validity rule and the warning period set in configuration. A useful operating model assigns responsibility for obtaining replacement evidence, checking what has changed and approving the new record. The tracker supports that work; it does not independently establish that a certificate is authentic, that a legal obligation applies or that a business is compliant.
04
Keep training evidence connected
The Help documentation also covers training administration. A programme can define subjects and accreditation information, with completed employee training linked to document certifications. Skills can be associated with the applicable certification so that the training record has a connection to the evidence being maintained.
The documented process creates a course from a programme, registers participants and schedules classes. Administrators capture session dates and venues, record attendance and, where appropriate, evaluation results. This is a specific extension of the document-tracking use case. If the requirement is only supplier certificates, the engagement should keep that scope clear rather than automatically introducing training administration.
05
Configure the responsibilities with the records
Braintree can use the source document categories and existing renewal process to scope the extension. The review should identify the entities in use, the people allowed to approve evidence, the required warning period and whether training records are part of the implementation.
Agree issuing authorities, document types, validity rules and entity associations.
Define defaults for new entities and how existing evidence will be captured.
Allocate receipt, review, approval and renewal responsibilities.
Validate role-centre visibility, expiry warnings and the selected approval workflow with sample documents.
EVIDENCE & DOCUMENTATION
See the work in context.
Document receipt and approval workflow
The guide shows entity-linked records, default document creation, attachment of received evidence and approval by a person with the appropriate authority.
Explore the documentation
BEFORE YOU DECIDE



