“Designed for Adagio”
Softrak is firmly committed to developing and enhancing its Adagio Developer Partner (ADP) program and wants to make every effort to encourage its Partners to integrate their products with Adagio. The closer the integration, the greater the ease of use for the end user and the shorter the learning curve for the channel. Our Business Partners are also looking to Softrak to provide some reassurance as to the quality of its Development Partner’s products. By sporting the “Designed for Adagio” logo, industry specific verticals that use Adagio as their accounting “back end” will be able to easily counter arguments from competitors offering integrated solutions.
Benefits
Softrak Development Partners that complete the “Designed for Adagio” process will be eligible to receive the following benefits:
- Inclusion in Softrak’s Price List
- Promotion in the AdagioNotes channel e.newsletter.
- Promotion in the Adagio KeyNotes end user e.newsletter.
- Participation in Softrak's direct mail, direct email and fax broadcasts.
- Mention in end user seminars.
- Mention at partner meetings and events.
- Access to Softrak’s webinar conferencing site for channel presentations
Objective
Increase the marketing visibility of 3rd Party products that provide a consistency of user experience with the core accounting modules and minimize the set-up and learning curve for this integration.
Methodology
Provide a documented set of specifications that 3rd Party products need to conform to and then allow them to display a “Designed for Adagio” logo on their product packaging and promotional literature while they are an Adagio Developer Partner. “Designed for Adagio” products would be eligible to appear in Softrak’s compatibility charts and price lists. We might decide to offer distribution for these products.
Minimum requirements for “Developed for Adagio” logo.
Objective
Assurance of quality and interface.
Methodology
ADPs must implement the Ledger interface described in this document. Adagio must be listed on their accounting integration tab, or they must create a build specifically to integrate with Adagio. “Developed for Adagio” logo is subject to a review by Softrak’s QA department.
Objective
Provide integration with Ledger that is operator error resistant and has similar integration as the other Adagio core modules. Ledger must display this message on start-up if transactions exist:
and must list the application in the retrieve transactions check list.
The 3rd Party developer is responsible for creating a file in Adagio Ledger’s data directory, with the correct extension. The format of the file is pure ASCII text with fixed length data elements and CRLF record delimiters. This file points to the file containing the actual transactions and has other control information. ADP’s with products that already produce a batch that can be retrieved (not imported) by Adagio Ledger already meet this requirement.
Other Requirements for “Designed for Adagio”
- In order to allow our Partners to maximize their learning curve, 3rd Party Developers using databases not accessible from ADS need to be using a database environment supported by Crystal Reports Standard Edition, or must have a function that will export the essential tables from their application to such a database.
- Forms must be customizable using some form of designer. Crystal Reports is an acceptable design tool.
Future Requirements
As Adagio matures, we will expect our Partners to gradually improve their integration with the core accounting modules. Some of this integration requires tools from Softrak which have not yet been written, so this integration requirement is several years off. Looking forward, you can expect us to look for:
- Easy (and automatic) departmentalization of g/l entries.
- G/L entries can be consolidated before being sent to the g/l.
- Product has pop-up finders for g/l accounts, customers, vendors etc to validate entry.
Technical Description
The name of the file is “GLBTHxxx.dat” where xxx is a 3 character code assigned by Softrak to the developer and dat is the company’s data extension. The ADP’s application is responsible for asking and storing the location of the Ledger data. The process for creating the transactions must make it impossible to miss or duplicate any entries destined for the general ledger without explicit operator overrides and warning messages. Preferably, transactions will be generated and written to the file as part of any posting process, without any required operator interaction. To the extent that an operator must explicitly create the Adagio Ledger batch, taking all the default options in any dialogues must automatically select the correct entries.
The 3rd Party product must append the records it generates. Adagio Ledger will empty (or delete) the file when it successfully retrieves the batch.
Resource File Format
The format of GLBTHxxx.dat is:
Line # | Description |
1. | The name of the application and version number. Modelled on: Adagio Receivables V6.8B |
2. | The path to the file containing the ledger transactions for retrieval. |
3. | The format of the batch. <Simple> or <Hdr/detail>. |
4. | <Source Codes> |
5. | Repeating lines containing the Source Codes and their descriptions needed by the 3rd Party product. Source Codes are 4 characters in 2, 2 character segments. The 1st 2 characters contain the application (AR=Receivables, AP=Payables, PR=Payroll, etc.) The second 2 characters indicate the transaction type (MC=Manual Check, IN=Invoice, CK=Check, etc). This is followed by a (maximum) 30 character description and then a CRLF pair. For example, Receivables would have the lines: 1234|--- ARINA/R Invoices ARCAA/R Cash ARADA/R Adjustment ARCOA/R Consolidation |
Last line | </Source Codes> |
Batch File Formats
There are two possible formats for importing transactions; simple and header/detail. Header/detail provides a tighter audit trail and is the preferred format.
Simple Batch File Format
Records in this file are identical in structure. They must contain this data in this order. Empty fields should be filled with spaces.
Field | Description | Size | Type |
1. | Record Description D – Detail C – Comment | 1 | CHAR |
Detail Record (Record Description = D) | |||
D | Detail Number Lines with identical detail numbers are grouped into a single transaction. | 4 | INT |
D | Entry Date (YYYYMMDD) | 8 | DATE |
D | Fiscal Period (01-13) | 2 | INT |
D | Account | 6 | RCHAR |
D | Department | 6 | RCHAR |
D | Subledger AR = Receivables AP = Payables IN = Invoices OE = Order Entry IC = Inventory PR = Payroll | 2 | RCHAR |
D | Trx Type IN = Invoice CK = Check MC = Manual Check AD = Adjustment CO = Consolidation | 2 | RCHAR |
D | Reference | 12 | CHAR |
D | Transaction Date (YYYYMMDD) | 8 | DATE |
D | Description | 30 | CHAR |
D | Amount (Credits are --‘ve) | 15 | CURRENCY |
D | Source Decimals (0,1,2,3,4) | 1 | INT |
D | Amt Source | 15 | CURRENCY |
D | Home Curr | 3 | CHAR |
D | Rate Type | 2 | CHAR |
D | Source Curr | 3 | CHAR |
D | Rate Date (YYYYMMDD) | 8 | DATE |
D | Exchg Rate | 15 | NUMBER |
D | Spread | 15 | NUMBER |
D | Rate Rep | 1 | CHAR |
D | Date Matching | 1 | CHAR |
Comment Record (Record Description = C) | |||
C | Comment | 60 | CHAR |
Header - Detail Batch File Format
This file groups balanced entries from a single transaction together. Balanced entries share the same Transaction Date and Fiscal Period.
Field | Description | Size | Type |
1. | Record Description H – Header D – Detail C – Comment | 1 | CHAR |
Header Record (Record Description = H) | |||
H | Entry Date (YYYYMMDD) | 8 | DATE |
H | Fiscal Period (01-13) | 2 | INT (0=Assign using date) |
H | Home Currency | 3 | CHAR |
H | Home Decimals (0,1,2,3,4) | 2 | INT |
Detail Record (Record Description = D) | |||
D | Account | 6 | RCHAR |
D | Department | 6 | RCHAR |
D | Subledger AR = Receivables AP = Payables IN = Invoices OE = Order Entry IC = Inventory PR = Payroll | 2 | RCHAR |
D | Trx Type IN = Invoice CK = Check MC = Manual Check AD = Adjustment CO = Consolidation | 2 | RCHAR |
D | Reference | 12 | CHAR |
D | Description | 30 | CHAR |
D | Amount (Credits are --‘ve) | 15 | CURRENCY |
D | Source Decimals (0,1,2,3,4) | 1 | INT |
D | Amt Source | 15 | CURRENCY |
D | Home Curr | 3 | CHAR |
D | Rate Type | 2 | CHAR |
D | Source Curr | 3 | CHAR |
D | Rate Date (YYYYMMDD) | 8 | DATE |
D | Exchg Rate | 15 | NUMBER |
D | Spread | 15 | NUMBER |
D | Rate Rep | 1 | CHAR |
D | Date Matching | 1 | CHAR |
Comment Record (Record Description = C) | |||
C | Comment | 60 | CHAR |
Dates are always in the form YYYYMMDD. Credits are negative amounts. Numbers are right justified with a leading minus sign if required.