Sage 50 Accounts: Data templates
When you configure the Sage 50 Accounts target system service, you use ReadSoft Online Connect to specify transaction templates that include data from ReadSoft Online that you want to send to Sage 50.
When you configure the Sage 50 Accounts target system service, you use ReadSoft Online Connect to specify transaction templates that include data from ReadSoft Online that you want to send to Sage 50.
You specify the data using plain-text constants and variables enclosed in percent marks.
- Constants - fixed values that you specify as text.
- Variables - dynamic values that are determined by invoice data or system data. Variables are enclosed in percent characters (%).
To specify a variable for an invoice field, enclose the Type name of the field in percent characters (%).
A variable can also be preceded by:
- # - to indicate that it is a system variable.
- @ - to indicate that it is a history variable.
- $ - to indicate that it is a user-defined variable.
Example
Supplier Name: %#Supplier.Name% Suppler Number: %#Supplier.ExternalId% InvNr: %InvoiceNumber%
System variables
You can specify system variables to obtain the values of system variables in ReadSoft Online.
- #Appendices
- #CreditInvoice
- #BatchPrefix
- #buyer.Type
- #buyer.Name
- #buyer.Id
- #Buyer.FieldName (where FieldName is a field name specified in ReadSoft Online XML (2.0))
- #buyer.ExternalId
- #buyer.Description
- #buyer.TaxRegistrationNumber
- #buyer.OrganizationNumber
- #buyer.Street
- #buyer.PostalCode
- #buyer.City
- #buyer.CountryName
- #buyer.PaymentTerm
- #buyer.PaymentMethod
- #buyer.CurrencyCode
- #buyer.BankAccounts
- #Currency
- #DateTime
- #Description
- #DocumentTypeSystemName
- #ImageFile2
- #NumberOfPagesFrontAndBack
- #NumberOfInvoicePages
- #NumberOfInvoicePagesFrontAndBack
- #NumberOfAppendixPages
- #NumberOfAppendixPagesFrontAndBack
- #Pages
- #Permalink
- #ProfileName
- #EndorserNumber
- #Supplier
- #Supplier.FieldName (where FieldName is a field name specified in ReadSoft Online XML (2.0))
- #SupplierDescription
- #supplier.Type
- #supplier.Name
- #supplier.Id
- #supplier.ExternalId
- #supplier.TaxRegistrationNumber
- #supplier.OrganizationNumber
- #supplier.Street
- #supplier.PostalCode
- #supplier.City
- #supplier.CountryName
- #supplier.PaymentTerm
- #supplier.PaymentMethod
- #supplier.CurrencyCode
- #supplier.BankAccounts
History variables
You can specify history variables to obtain the user or the date and time of a specific process. You construct a history variable using the format, @UserOrDateX, where UserOrDate specifies whether you want the user or the date, and X specifies the numerical code of the process you want to return. For example, use "@Date0" to return the date a document was created.
| Process status | Numerical code |
|---|---|
| DocumentCreated | 0 |
| DocumentExtractionInProgress | 30 |
| DocumentExtractionSucceeded | 40 |
| DocumentPendingManualVerification | 45 |
| DocumentPendingCorrection | 46 |
| DocumentCorrectionFlowStarting | 47 |
| DocumentCorrectionFlowInProgress | 48 |
| DocumentCorrectionFlowDone | 49 |
| DocumentRejectedDuringVerification | 50 |
| DocumentRequestForInformationDuringVerification | 55 |
| DocumentManuallyVerified | 60 |
| DocumentPendingRegistration | 61 |
| DocumentRegistrationInProgress | 62 |
| DocumentRegistrationSucceeded | 63 |
| DocumentRegistrationFailed | 64 |
| DocumentPendingApproval | 65 |
| DocumentApprovalStarting | 79 |
| DocumentApprovalInProgress | 66 |
| DocumentApproved | 67 |
| DocumentApprovalSucceeded | 68 |
| DocumentApprovalRejected | 69 |
| DocumentRequestForInformation | 70 |
| DocumentPendingAllocation | 71 |
| DocumentPendingPost | 74 |
| DocumentPostInProgress | 75 |
| DocumentPostSucceeded | 76 |
| DocumentPostFailed | 77 |
| DocumentAssignedToUser | 78 |
| DocumentPendingBatchRegistration | 80 |
| DocumentPendingBatchPost | 81 |
| DocumentValidationFailed | 82 |
| DocumentPendingExport | 90 |
| DocumentExportPostponed | 91 |
| DocumentExportInProgress | 95 |
| DocumentExportFailed | 99 |
| DocumentExportSucceeded | 100 |
| DocumentSentToStorage | 200 |
| DocumentCommentAdded | 201 |
| LineItemExtractionUsed | 202 |
| DocumentFailed | 900 |
| DocumentDeleted | 1000 |
User-defined variables
You can specify user-defined variables to obtain the values of the user-defined variables in ReadSoft Online. User-defined variables are different for each integration, but they might look something like this:
- $WebEye.CustomerID
- $WebEye.BatchID
- $WebEye.BuyerID
- $WebEye.OutputImageFormat
- $WebEye.DocumentID
- $ExternalId
- $UploaderUserName
- $OriginalFileName
- $BatchTrackId
- $ReceiveTime
- $DocumentId
- $VerifierUserName
Handling long transaction headers
By default, the Transaction header details template is limited to 60 characters. To work around this issue, you can use a limited set of C# string functions to manipulate the header details. You can use the following C# functions:
|
|
Example
If you want to limit the supplier name in the transaction header to 30 characters, you can type the following in the Transaction header details template setting in the ReadSoft Online Connect configuration wizard:
%SupplierName%.Substring(0,30)