Open ekoskent opened 5 years ago
A voucher can be an invoice, a receipt, a rent agreement, payroll slip.. Some vouchers are added in structural formats (e.g. XML) from which the accounting entries may be automatically created. Some vouchers are created by hand and they can be stored as PDF-copies from which the accounting entries must be able to be created also manually.
Discussed with David to creating one general level API for submitting and requesting business documents (vouchers) that replaces the separate APIs for invoices, bank statements... params: companyID, documentType
Discussed with David to creating one general level API for submitting and requesting business documents (vouchers) that replaces the separate APIs for invoices, bank statements... params: companyID, documentType
The documentType should be an identifier to declare the format (and version) used to represent the data (PDF, UBL, Finvoice...) Suggest to use notion from PEPPOL see 4.2 Document Type Identifier Values: https://peppol.eu/wp-content/uploads/2017/12/PEPPOL_Policy-for-use-of-identifiers-300-11_certificates.pdf
We also need to identify the voucher type (purchase invoice, sales invoie, order, receipt...). An enumerated list of possible values should probably be drafted for this? Suggest to add also voucherType as a parameter
As a: business owner / user of a business system I wish to: add a business document of any business transaction in to my business transaction storage (this includes other document types than vouchers) So that: My accounting system may create the possibly accounting entries based on the business document data and that I can give access to the business document data to other systems or users that want to use it.
Related to epic: Informasjonsforvaltning/behov#315
Link to design: Link to solution archietecture:
This is a generalization of the APIs for Invoice, Bank Statements, Order and Receipts