OverviewThis section of the knowledge base provides information for developers of Salesforce and Accounting Seed. Accounting Seed uses the Salesforce API which is fully documented at https://developer.salesforce.com/. Accounting Seed extends the Salesforce API with Global Classes for our posting process of Billings, Accounts Payable, and Journal Entries.
|Source Object Name||Global Posting/Unposting Class Accessible Via Apex||Rest API for Posting/Unposting|
|Billing & Billing Lines||Yes||Yes|
|Cash Receipt||Yes as of 2.21||No|
|Billing Cash Receipt||No, But posts automatically||No|
|Payable & Payable Line||Yes||No|
|AP Disbursement||No, But posts automatically||No|
|Amortization Entry||Yes as of 2.21||No|
|Time Card Day||No||No|
|Purchase Order Inventory Movement (Part of ERP Package)||No, But posts automatically||No|
|Inbound Inventory Movement (Part of ERP Package)||No, But posts automatically||No|
|Manufacturing Inventory Movement (Part of ERP Package)||No, But posts automatically||No|
|Outbound Inventory Movement (Part of ERP Package)||No, But posts automatically||No|
Accounting Seed made a deliberate decision to maintain the flexibility of the Salesforce platform and build Accounting Seed as natively as possible. This means you can customize and configure our objects and page layouts just like you can with any custom object in Salesforce.
Ultimately, any object in Accounting Seed can be integrated to from outside of the General Ledger tables described above. However, the three most common integration points are the Billing, Payable and Journal Entry.
Customizable Objects and Page Layouts
Custom Fields, Workflow Rules, Process Flows, Approval Rules, Validation Rules, and more are all available tools that Salesforce supplies and can be leveraged in the same way with Accounting Seed.
Accounting Seed is often used with other AppExchange apps that are developed in the same open architecture, native way.
Document generation products can also be used to generate customer/vendor facing documents such as Invoices, Statements, Purchase Orders, and Packing Slips.
There are, however, three Accounting Seed objects that drive the integrity of the General Ledger data that we prevent anyone from editing either manually, via the API, or through declarative Salesforce tools. They are:
Financial Cube Object
Financial Cube Transaction Object
Commonly Customized Functions
There are a few areas of customization we see customers request that Accounting Seed will not be building into the application. These areas tend to be something that each customer does differently so they make ideal customization candidates. Here are five of the most common:
Expense Allocations: For example spreading expenses of a shared resource across multiple business units.
Sales Commissions: This is unique to each customer’s sales compensation plan, the Opportunity, Billing, and Cash Receipt data is all available to be used for this calculation.
Revenue Recognition: This is unique to each customer’s business model. Percent complete of the sale or job, as well as amount invoiced to date are both components of this solution.
Inter-company Transactions: When a company has subsidiaries or multiple related entities, it is almost always necessary to make adjusting entries to avoid counting transactions in both sets of books. These are generically known as inter-company transactions and are unique to the companies operating practices.