Update a ledger receipt.
Supported ledger receipt types are journals, sales invoice ledger receipts, travel invoice ledger receipts, expense invoice ledger receipts and purchase ledger invoice receipts. For defining the ledger accounts, dimensions, VAT status or other accounting information for an invoice, use this endpoint.Use "createReconciliation=true" parameter to generate reconciliation row automatically. See Transaction model for more details
Request
- Base URL: https://pts-api.procountor.com/api
- URL: https://pts-api.procountor.com/api/ledgerreceipts/{receiptId}
- Auth: HTTP bearer
Path parameters
Ledger receipt identifier
Query parameters
Enable automatic generation of reconciliation row
Request body
Unique identifier of the ledger receipt. Generated by Procountor and present in the object returned.
Ledger receipt type. Use JOURNAL for creating ledger receipts (vouchers) containing ledger transactions without linkage to pre-existing resources. Other types are automatically generated by Procountor for holding accounting information for e.g. invoices. Types allowed for POST = JOURNAL. Types allowed for PUT = JOURNAL, SALES_INVOICE, PURCHASE_INVOICE, TRAVEL_INVOICE, BILL_OF_CHARGES Types allowed for GET listed below
Ledger receipt status. Status of a ledger receipt equals the status of the linked invoice. All ledger receipts are initially created with status UNFINISHED. For journals, possible statuses are UNFINISHED, APPROVED and INVALIDATED. Ledger receipt statuses cannot be directly modified through the API.
Ledger receipt name.
Ledger receipt date. Must not be in a closed fiscal period. See GET /fiscalyears for a list of fiscal years.
Ledger receipt VAT type.
Ledger receipt VAT status. This can be overridden on transaction level. Use here the numeric parts of VAT status codes listed in "VAT defaults" in Procountor. For example, for VAT status code "vat_12", use value 12. The VAT status used must be enabled for the current receipt type (sales/purchase).
Ledger receipt VAT country. Only for JOURNAL types of ledger receipts. Requires a special right for foreign VATs. See Address.country in POST /invoices for a list of allowable values.
ID of the linked invoice. For sales and purchase invoice ledger receipts, this refers to the invoice the receipt holds accounting data for. For journal receipts, an invoice is automatically generated to store certain data fields. Use this ID in POST /attachments endpoint.
Number of the ledger receipt.
Invoice notes. Linked to Invoice.notes. Not visible on ledger receipt printouts. Use \n as line break. Max length 10000.
Number of the linked invoice. Automatically generated by Procountor.
Notes made by the accountant. Visible on ledger receipt printouts.
Transaction description. This is a summary description for any transactions belonging to the ledger receipt.
Receipt validity time.
Start date of the receipt period. If set, must precede the end date of the period.
End date of the receipt period. If this and the start date are set, this must be after the start date.
Technical ID for the business partner. Link the related invoice to a customer or supplier in the business partner register. If supplied, the company must have this partner ID in the corresponding register.
Partner code. Identifier for the related company or person. May represent a business ID, national identification number (HETU in Finland) or an account number, depending on the receipt type.
Ledger receipt version timestamp. Automatically generated by Procountor and updated every time the receipt is modified. When using PUT /ledgerreceipts, it is required to include the latest version timestamp of the receipt to the request. This prevents conflicts if the receipt is being modified from several sources.
Accounting depreciation method for the receipt.
VAT date to be used if payment based VAT is enabled
Example request
{
"vatProcessing": "SWEDEN",
"attachments": [
{
"name": "Picture.jpg"
}
]
}Response
Ledger receipt was successfully updated.
Unique identifier of the ledger receipt. Generated by Procountor and present in the object returned.
Ledger receipt type. Use JOURNAL for creating ledger receipts (vouchers) containing ledger transactions without linkage to pre-existing resources. Other types are automatically generated by Procountor for holding accounting information for e.g. invoices. Types allowed for POST = JOURNAL. Types allowed for PUT = JOURNAL, SALES_INVOICE, PURCHASE_INVOICE, TRAVEL_INVOICE, BILL_OF_CHARGES Types allowed for GET listed below
Ledger receipt status. Status of a ledger receipt equals the status of the linked invoice. All ledger receipts are initially created with status UNFINISHED. For journals, possible statuses are UNFINISHED, APPROVED and INVALIDATED. Ledger receipt statuses cannot be directly modified through the API.
Ledger receipt name.
Ledger receipt date. Must not be in a closed fiscal period. See GET /fiscalyears for a list of fiscal years.
Ledger receipt VAT type.
Ledger receipt VAT status. This can be overridden on transaction level. Use here the numeric parts of VAT status codes listed in "VAT defaults" in Procountor. For example, for VAT status code "vat_12", use value 12. The VAT status used must be enabled for the current receipt type (sales/purchase).
Ledger receipt VAT country. Only for JOURNAL types of ledger receipts. Requires a special right for foreign VATs. See Address.country in POST /invoices for a list of allowable values.
ID of the linked invoice. For sales and purchase invoice ledger receipts, this refers to the invoice the receipt holds accounting data for. For journal receipts, an invoice is automatically generated to store certain data fields. Use this ID in POST /attachments endpoint.
Number of the ledger receipt.
Invoice notes. Linked to Invoice.notes. Not visible on ledger receipt printouts. Use \n as line break. Max length 10000.
Number of the linked invoice. Automatically generated by Procountor.
Notes made by the accountant. Visible on ledger receipt printouts.
Transaction description. This is a summary description for any transactions belonging to the ledger receipt.
Receipt validity time.
Start date of the receipt period. If set, must precede the end date of the period.
End date of the receipt period. If this and the start date are set, this must be after the start date.
Technical ID for the business partner. Link the related invoice to a customer or supplier in the business partner register. If supplied, the company must have this partner ID in the corresponding register.
Partner code. Identifier for the related company or person. May represent a business ID, national identification number (HETU in Finland) or an account number, depending on the receipt type.
Ledger receipt version timestamp. Automatically generated by Procountor and updated every time the receipt is modified. When using PUT /ledgerreceipts, it is required to include the latest version timestamp of the receipt to the request. This prevents conflicts if the receipt is being modified from several sources.
Accounting depreciation method for the receipt.
VAT date to be used if payment based VAT is enabled
Example response
{
"vatProcessing": "SWEDEN",
"attachments": [
{
"name": "Picture.jpg"
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.