How fields appear in the field picker
Each field in the Data Analytics field picker carries a type mark and is added to the report as one column. Every field is optional, and a blank report starts with no columns, so none of the fields below is in a report until you add it. The Type column in the tables on this page uses these values:
Status fields that answer a yes-or-no question read Yes or No. Fields marked with a Line badge come from a line record, so a report that uses them returns one row per line.
Columns that share a label show the same header, with nothing to mark which record each one comes from. For example, a GL Entries report that joins both a customer and a vendor and adds Country from each shows two Country columns. Use the column order under Columns to keep track of which is which.
GL Entries fields: record and dates
The GL Entries record type returns one row per posted general ledger entry. The fields in this group identify the source record and its dates.GL Entries fields: account and company
These GL Entries fields describe the account and company an entry posts to. To add every field of the account itself, such as its type or parent, join Chart of Accounts (see GL Entries join paths).GL Entries fields: amounts and currency
The GL Entries amount fields come in two currencies: the transaction currency the record was entered in, and the base currency of the entry company. Debit and Credit stay in the transaction currency.
Base amounts are the transaction amount multiplied by Transaction FX Rate, rounded to two decimal places. Amount (Base) and Transaction Currency Amount are signed by the account’s normal balance: positive when the entry increases the account’s normal balance and negative when it decreases it. A debit to an expense account is positive, and a debit to a revenue account is negative.
GL Entries fields: customer, vendor, and billable
These GL Entries fields show who an entry relates to and whether its source line is billable to a customer.GL Entries fields: ship-to and audit
These GL Entries fields carry the source record’s ship-to address and its audit history.GL Entries custom fields and classifications
GL Entries also list your organization’s custom fields and classifications, so you can report on GL activity by the same dimensions you use on transactions.- Custom fields: Each active custom field in your organization appears as one column named after the custom field. The value comes from the entry’s source record, so the column is empty for entries whose source record type the custom field doesn’t apply to. A custom field that applies only to customers, vendors, or accounts is always empty here. To report on those values, join Customers, Vendors, or Chart of Accounts and use the field from the joined record.
- Classifications: Each classification tree, such as Department or Location, appears as one column named after the tree, holding the entry’s value in that tree.
GL Entries join paths
Join paths from GL Entries add the fields of a related record to each entry row. Each path below is many-to-1, so it never adds rows. Paths appear under Suggested join paths from GL Entries when you choose Add join.
A report joins each record type once. Once you add GL Entry → Customer, the GL Entry → Line Customer path no longer appears, and the same applies to the two vendor paths. Pick the record-level or line-level path based on which customer or vendor you want to report on.
Customer fields
The Customers record type returns one row per customer, and the same fields are available when you join a customer from another record type. The tables below list the identity and contact fields first, then terms, tax, and company settings.Customer terms, tax, and company fields
These Customers fields hold the defaults DualEntry applies to the customer’s transactions.Customer addresses, custom fields, and classifications
Each Customers address is available as one full-address field and as separate parts, for both the billing and the shipping address.
The customer’s custom fields appear as one column per custom field, and each classification tree appears as one column named after the tree.
Vendor fields
The Vendors record type returns one row per vendor, and the same fields are available when you join a vendor from another record type.Vendor payment, tax, and company fields
These Vendors fields hold the defaults DualEntry applies to the vendor’s bills and payments.Vendor address, custom fields, and classifications
The Vendors address is available as one full-address field, as the address entered in a single text box, and as separate parts.
The vendor’s custom fields appear as one column per custom field, and each classification tree appears as one column named after the tree. The vendor’s taxpayer identification number and bank account and routing numbers aren’t available in Data Analytics.
Chart of Accounts fields
The Chart of Accounts record type returns one row per account, and the same fields are available when you join an account from GL Entries or Bill Lines, or join an income account from Invoice Lines.Account hierarchy, company, and bank fields
These Chart of Accounts fields place the account in the account tree and show its company and bank settings.
The account’s custom fields appear as one column per custom field. Bank account numbers aren’t available in Data Analytics.
Invoice Lines fields
The Invoice Lines record type returns one row per invoice line, and every field carries the Line badge.
Amounts on a line for a discount item are negative. Each classification tree also appears as one line-level column named after the tree.
Bill Lines fields
The Bill Lines record type returns one row per bill line, and every field carries the Line badge.Bill line billable fields
These Bill Lines fields track a bill line that you bill on to a customer.
Each classification tree also appears as one line-level column named after the tree.
Invoice Lines and Bill Lines join paths
Join paths from Invoice Lines and Bill Lines add the fields of the header invoice or bill and of the records the line or its header points to. Some paths reach the header’s customer, vendor, terms, or company directly, so you don’t need to join the invoice or bill first. Every path in the two tables below is many-to-1, so none of them adds rows.Invoice Lines join paths
This table lists every join path from Invoice Lines, by its label in the join list.Bill Lines join paths
This table lists every join path from Bill Lines, by its label in the join list.
A report joins each record type once, so paths that lead to the same record type are alternatives. For example, on Bill Lines you can join Bill Line → Vendor or Bill Line → Bill Vendor, not both.
Header amounts on line reports
When a line report joins its header record, for example Invoices from Invoice Lines, grouped totals count each header amount once per invoice or bill, not once per line. A header total such as the invoice amount therefore doesn’t multiply by the number of lines.Fields not available in Data Analytics
Some values aren’t offered as fields, either to protect sensitive data or because Data Analytics doesn’t calculate them. The fields on this page don’t include:- A vendor’s taxpayer identification number, bank account number, or routing number
- Bank account numbers on accounts
- A running balance or beginning balance on GL entries, or an account’s current balance
- Item and quantity on GL entries
- Custom fields on invoice and bill lines