Object Name in SF to import to:

Payable Header Template to "Payable" Object

Payable Lines Template to "Payable Line" Object

Related Accounting Seed University and Knowledge Base Articles:

https://support.accountingseed.com/hc/en-us/sections/203878147-Creating-Payables-Vendor-Invoices-
https://www.accountingseed.com/accounting-seed-university-cash-out-lesson-1

Guidance:

Note that the column header titles correspond exactly to what the reference fields are named. This enables the Imp
map the fields in the template to the object. These columns are not meant to be an exhaustive list of all the fields av
object, but only the most commonly used. You can easily add additional fields to import by reviewing the object and
column for that field. To maintain auto-mapping, please keep the same naming convention in the template as in the

1. Headers and Lines have a master-detail relationship in Accounting Seed. To maintain this relationship, the Payabl
worksheet 2) must be created prior to uploading Payable Line (on worksheet 3). Accounting Seed is a period based a
system. Therefore, if the Accounting Period is left blank, the transaction will post by default to the period that the th
Payable [Header] falls within.

2. Payable field (column A) of worksheet 3 (Payable Line) must be equal to Payable Name field (column A) of worksh
match up and establish the master-detail relationship between Payable Headers and Payable Lines.

If you are only uploading one Payable, it may be easier to manually create the header in the system and then upload
this header.

3. This is a two step process.

A. Worksheet "2. Payable" is used to upload Payable headers. Some users choose to manually enter the header(s) an
the lines.

B. Worksheet "3. Payable Line" uploads the individual line(s) of the Payable.

4. Save your file as a *.csv file. Delete any rows and columns that are not pertinent to the upload (i.e. Instruction ro
etc.). Delete any worksheets that are not pertinent to the upload. The Data Loader App and Data Import Wizard too
multiple worksheets in a workbook.
5. Upload either using Data Import Wizard or Data Loader App. Please see following series of Salesforce help knowl
the importing process and how to use the Data Import Wizard or Data Loader App:

https://help.salesforce.com/articleView?id=importing.htm&type=5

6. Once upload of the is complete and successful, verify that your upload is successful by reviewing the Results file g
import and verify that the records were created in Accounting Seed.
A Payable can have either the Account (Vendor), Contact or User (Employee) as the Payee. Choose only ONE for
each Payable.

When populating Look-up fields, it is always recommended to use the SF ID instead of the Name of the record.
Vendor Vendor SF ID Contact Contact SF ID Employee
Alpha Communications 0014100001UqF6l

Key
Required Field
Instructional Text
Conditionally Required
Sample Data
Payable Object Field
 Used to specify accounting
period for financial reporting.
If left blank, this will default to
e Payee. Choose only ONE for the related period of the issue
date. Accounting period must
Date of the Vendor have a value of "Open" in
d of the Name of the record. invoice. order to be selected.
Employee SF ID Issue Date Accounting Period
7/31/2018 2018-07
 If left blank, the Due Date equals
the Issue Date plus the Payable Days
Due on the associated Account
(Vendor) record. Otherwise, the
Due Date defaults to the Issue Date. Enter the invoice number
If populated, it will override this here. This will print on the
automation. check stub.
Due Date Payee Reference
9879
 Used in approvals of
Payable records. You
Used to track an extra number can choose "Approved"
besides the Vendor invoice number. or "In Process" by If you are using
For example, a policy number may be default. Posted cannot multi-ledger, enter
entered here and this will flow to the be selected, but rather the related ledger
check stub. done after the import. value
Proprietary Payable Number Posting Status Ledger
Policy 1234 Approved
 When populating Look-up
fields, it is always
This is the Payable Name recommended to use the Typically, the same as
generated once the Payable SF ID instead of the Name the Payable Header
Header has been uploaded of the record. Issue Date.

Payable Name Payable SF ID Date

AP-00137 a0Z41000005Jiva 7/31/2018

Key
Required Field
Instructional Text
Conditionally Required
Sample Data
Payable Object Field
Payable Line Object Field
 When populating Look-up fields,
This GL account will be debited it is always recommended to Enter in
when the related Payable is use the SF ID instead of the quantity if
posted Name of the record. necessary

Expense GL Account Expense GL Account SF ID Quantity

6000-Advertising 2
Enter the amount. This Lookup to Accounting Variable object. Specific values corre
is the total that will be Department; GL Variable 2 can be used for Division; etc. If the
posted to the ledger. source transactions like Billings, Payable
The system will not
multiply quantity x Can be used for approval If populated here, this value will override the variable value set
amount. processes befo
GL Variable 1
Amount Internal Comment GL Variable 1 SF ID
1000 Advertising in July 2018 Department A
Department B
g Variable object. Specific values corresponding to the business segment. For example, GL Variable 1 is usually used for
2 can be used for Division; etc. If the variable values are added to the Account or Product record, the values will default to
urce transactions like Billings, Payables, and Journal Entries. Account has precedence over Product.

ue will override the variable value set up on the Account or Product. These values must already be entered into the system
before populating them here.
GL Variable 2 GL Variable 3
GL Variable 2 SF ID GL Variable 3 SF ID GL Variable 4
Division B
Division A
Variable 1 is usually used for
record, the values will default to When populating Look-
Product. If this expense up fields, it is always If this expense
relates to a recommended to use relates to a
ready be entered into the system product, enter the SF ID instead of the job/project, then
that here Name of the record. enter that here

GL Variable 4 SF ID Product Product SF ID Project

Catering Services
 When populating
Look-up fields, it is Used to document a
always specific task or When populating Look-
recommended to phase of a project. up fields, it is always
use the SF ID instead If a project is recommended to use
of the Name of the selected, then this the SF ID instead of the
record. must be populated Name of the record.

Project SF ID Project Task Project Task SF ID