Invoice Monitor Service Description
Status: 01.2026 Version: 1.0
1. Introduction
1.1 Cloud-Optimized Extension
The Invoice Monitor solution is developed as a "Cloud-Optimized" extension following Microsoft's Universal Code Initiative guidelines. This essentially means that no OnPrem development takes place. It can be assumed that a "Cloud-Optimized" extension will also run on OnPrem installations.
1.2 Web Services
Communication between smart invoice and BC occurs exclusively via web services. The Invoice Monitor provides information and functions through Dynamics 365 Business Central API objects. This can be accomplished through Pages, Queries, Bound Actions, or Webhooks.
1.3 Country Versions
The Invoice Monitor is developed as an extension to Business Central in the base version "DE".
1.4 Language Versions
The development of the Invoice Monitor is carried out in multilingual format. The languages EN-US and DE-DE are permanently maintained during development.
1.5 Credit Memos
In the following text, only invoices or purchase invoices are mentioned. The statements that apply to invoices also apply to credit memos, without specific reference in the text.
1.6 Extensions
The Invoice Monitor was specifically developed and tested for seamless collaboration with the standard scope of Microsoft Dynamics 365 Business Central. This ensures reliable and smooth use of the intended functions. Compatibility with third-party extensions or apps is not part of the scope of services. No warranty can be given for resulting malfunctions or limitations.
2. Objectives
The Invoice Monitor enables structured and automated transfer and processing of purchase documents in Microsoft Dynamics 365 Business Central. The solution supports a wide range of data content as well as direct integration into existing processes.
3. Features Overview
The following list shows all scenarios currently supported by the Invoice Monitor in the Business Central standard. Scenarios that deviate from this list must be considered project-specifically and may need to be evaluated separately.
3.1 Processing of Purchase Documents
The Invoice Monitor supports the transfer and further processing of the following document types:
- Purchase Invoices
- Purchase Credit Memos
3.2 Supported Document Lines
Both item and general ledger account lines are processed. Additionally, charges (item charges) are supported, including the associated assignment information.
3.3 Document Links
It is possible to uniquely assign document lines to an order or receipt reference, which ensures traceability in the system.
3.4 Dimension Support
- At document header level: Shortcut dimensions 1 and 2 are processed.
- At document line level: Up to 8 dimensions (Dimension 1–8) can be transferred.
3.5 Document Completion with Validation
Before final posting, the document is fully validated. All transferred fields are checked for consistency and validity to detect errors early and prevent subsequent problems.
3.6 Posting via API or User Interface
The posting of prepared documents can be done either automatically via an API or manually through specially provided pages in the Invoice Monitor module.
3.7 Integration of Swiss QR Invoice
Information from Swiss QR invoices can be extracted and transferred to the Microsoft QR-Bill app – for complete digital processing according to local requirements.
3.8 Custom Fields
Up to 20 freely usable custom fields are available.
Supported data types:
- Text
- Code
- Integer
- Decimal
- Date
Values are assigned to the field according to the setup (not validated).
3.9 Foreign Currencies
The Invoice Monitor supports the processing and posting of invoices in foreign currencies according to the standard functions of Business Central.
3.10 Document Display
On the Invoice Monitor card and Invoice Monitor list, the following are available for document display:
- Buttons with configurable hyperlinks
- iFrames with configurable hyperlinks
4. Technical Details
4.1 API Endpoints
4.1.1 rmDocumentHeaders (Document Header)
The transfer of invoice data is structured via an API interface. The following fields are supported in the document header:
| Field Name | Field Name | Field Name | Field Name |
|---|---|---|---|
| entryArchiveID | entryBarcode | entryWorkflowStatus | skipValidation |
| custom1 | custom2 | custom3 | custom4 |
| custom5 | custom6 | custom7 | custom8 |
| custom9 | custom10 | custom11 | custom12 |
| custom13 | custom14 | custom15 | custom16 |
| custom17 | custom18 | custom19 | custom20 |
| custom100 | custom101 | custom102 | custom104 |
| custom105 | custom106 | custom107 | custom108 |
| custom109 | documentType | buyFromVendorNo | buyfromVendorName |
| postingDescription | buyFromAddress | buyFromAddress2 | buyFromCity |
| buyFromCounty | buyFromPostCode | buyFromCountryRegionCode | buyFromContactNo |
| buyFromContact | documentDate | postingDate | dueDate |
| incomingDocumentEntryNo | vendorInvoiceNo | vendorCrMemoNo | purchaserCode |
| vendorOrderNo | campaignNo | orderAddressCode | responsibilityCenter |
| assignedUserID | status | jobQueueStatus | currencyCode |
| expectedReceiptDate | pricesIncludingVAT | vatBusPostingGroup | vendorPostingGroup |
| paymentTermsCode | paymentMethodCode | reasonCode | shortcutDimension1Code |
| shortcutDimension2Code | paymentDiscountPercent | pmtDiscountDate | journalTemplName |
| taxLiable | taxAreaCode | shipmentMethodCode | paymentReference |
| creditorNo | onHold | locationCode | shipToName |
| shipToAddress | shipToAddress2 | shipToCity | shipToCounty |
| shipToPostCode | shipToCountryRegionCode | shipToContact | payToVendorNo |
| payToName | payToAddress | payToAddress2 | payToCity |
| payToCounty | payToPostCode | payToCountryRegionCode | payToContactNo |
| payToContact | transactionSpecification | transactionType | transportMethod |
| entryPoint | areaReporting | lastModifiedAt | amount |
| amountIncludingVat | vatAmount | workflowUser | pmtDiscountDateAmount |
| workflowStartStatus | workflowOnHoldStatus | workflowResumeStatus | workflowCancelStatus |
| workflowRestartStatus | workflowApprovalStatus | workflowRejectStatus | documentFinalReturnStatus |
| documentFinalReleaseStatus | documentFinalPostingStatus | purchaseOrderNo | unpostedInvoiceNo |
| unpostedCreditNoteNo | postedInvoiceNo | postedCreditNoteNo | documentLocationUrl |
4.1.2 rmDocumentHeadersArchive (Document Header Archive)
Identical field structure as rmDocumentHeaders.
4.1.3 rmDocumentLines (Document Line)
| Field Name | Field Name | Field Name | Field Name |
|---|---|---|---|
| entryNo | lineNo | factualVerfier | approvingManager |
| custom1 | custom2 | custom3 | custom4 |
| custom5 | custom6 | custom7 | custom8 |
| custom9 | custom10 | custom11 | custom12 |
| custom13 | custom14 | custom15 | custom16 |
| custom17 | custom18 | custom19 | custom20 |
| type | no | itemReferenceNo | icPartnerCode |
| icPartnerRefType | icPartnerReference | variantCode | nonstock |
| genProdPostingGroup | vatProdPostingGroup | description | description2 |
| returnReasonCode | locationCode | binCode | quantity |
| unitOfMeasureCode | unitOfMeasure | directUnitCost | indirectCostpercent |
| unitCostLCY | unitPriceLCY | taxLiable | taxAreaCode |
| taxGroupCode | useTax | lineDiscountpercent | lineAmount |
| lineDiscountAmount | allowInvoiceDisc | invDiscountAmount | allowItemChargeAssignment |
| qtyToAssign | qtyAssigned | jobNo | jobTaskNo |
| jobPlanningLineNo | jobLineType | jobUnitPrice | jobLineAmount |
| jobLineDiscountAmount | jobLineDiscountpercent | jobTotalPrice | jobUnitPriceLCY |
| jobTotalPriceLCY | jobLineAmountLCY | jobLineDiscAmountLCY | prodOrderNo |
| blanketOrderNo | blanketOrderLineNo | insuranceNo | faPostingDate |
| budgetedFANo | faPostingType | depreciationBookCode | deprUntilFaPostingDate |
| deprAcquisitionCost | duplicateInDepreciationBook | useDuplicationList | applToItemEntry |
| deferralCode | documentNo | originalLineNo | grossWeight |
| netWeight | unitVolume | unitsPerParcel | currencyCode |
| shortcutDimension1 | shortcutDimension2 | shortcutDimension3 | shortcutDimension4 |
| shortcutDimension5 | shortcutDimension6 | shortcutDimension7 | shortcutDimension8 |
| vatBusPostingGroup | genBusPostingGroup | orderNo | orderLineNo |
| receiptNo | receiptLineNo | purchLineDocNo | purchLineLineNo |
| amountIncludingVat |
4.1.4 rmDocumentLinesArchive (Document Line Archive)
Identical field structure as rmDocumentLines.
4.1.5 rmItemChargeAssignments (Item Charge Assignments)
| Field Name | Field Name | Field Name | Field Name |
|---|---|---|---|
| entryNo | rmLineNo | documentType | documentNo |
| documentLineNo | appliestoDocType | appliestoDocNo | appliestoDocLineNo |
| lineNo | itemChargeNo | itemNo | description |
| qtyToAssign | qtyAssigned | amountToAssign | grossWeight |
| unitVolume | unitCost | qtyToReceiveBase | qtyReceivedBase |
| qtyToShipBase | qtyShippedBase | documentDate | kmirmEntryNo |
| kmirmLineNo |
5. User Interface
5.1 Invoice Monitor List
The Invoice Monitor list provides an overview of all existing documents in the system.
5.2 Invoice Monitor Card
The Invoice Monitor card enables detailed viewing and editing of individual documents.
6. Licensing Model and Deployment
OnPrem
License:
- Activation of the granule via the BC partner (chargeable)
- Send information regarding Voice-ID of the BC partner via email to ecm-support@konicaminolta.de
Deployment:
- Via Runtime App
- Send information regarding BC version of the BC partner via email to ecm-support@konicaminolta.de
Cloud
License:
- AppSource (Tenant-ID required)
- Licensing via AppSource
Deployment:
- AppSource
Support
For support inquiries, please contact: ecm-support@konicaminolta.de