Skip to main content

GoldFinch Integration Capabilities and Workflows

Updated

GoldFinch integrations connect ERP processes with Salesforce applications and external business systems. Each integration is designed around the records, business events, and responsibilities involved in the customer’s workflow.

This article provides a high-level overview. Authorized customers and implementation partners can access detailed configuration, field mappings, authentication, and troubleshooting instructions.

Common Integration Capabilities

Depending on the connected system, GoldFinch integrations may support:

  • Creating or updating records
  • Importing and exporting transactions
  • Scheduled data synchronization
  • Near-real-time processing
  • Status and reference updates
  • File-based data exchange
  • API-based communication
  • Validation and exception reporting
  • Reconciliation between systems
  • Salesforce workflow and approval automation

Customer and Vendor Information

Integrations may exchange customer, vendor, contact, address, payment-term, tax, and related master data.

Before implementation, the project team determines which system owns each type of information. Establishing a clear source of truth helps prevent duplicate or conflicting updates.

Item and Pricing Information

GoldFinch may exchange:

  • Item numbers and descriptions
  • Units of measure
  • Product classifications
  • Prices and discounts
  • Inventory availability
  • Barcodes or external product identifiers

The supported fields and update direction depend on the connected application and business requirements.

eCommerce Order Workflow

A typical eCommerce integration may include:

  1. A customer places an order through an online store.
  2. The system transfers customer and order information to GoldFinch.
  3. GoldFinch processes inventory allocation, fulfillment, and invoicing.
  4. GoldFinch returns shipment status and tracking information to the eCommerce system.
  5. Payment and settlement information is recorded or reconciled.

The actual workflow may differ depending on the eCommerce platform, payment provider, warehouse process, and accounting system.

Shipping and Fulfillment Workflow

A typical shipping integration may include:

  1. GoldFinch sends shipment information to the shipping application.
  2. Users select a carrier and service and generate shipping documents.
  3. The shipping system returns the tracking number, shipping cost, and status.
  4. GoldFinch updates the related order or shipment.
  5. GoldFinch may share tracking information with the customer or another connected system.

EDI Workflow

An EDI workflow may include:

  1. A trading partner sends an electronic purchase order.
  2. The EDI provider validates and translates the document.
  3. GoldFinch creates or updates the appropriate transaction.
  4. GoldFinch sends acknowledgments, shipment information, or invoices.
  5. Authorized users review and correct exceptions.

Supported EDI documents and mapping requirements are determined separately for each trading partner.

Payment Workflow

A payment integration may allow users to:

  1. Initiate or receive a payment through the connected provider.
  2. Associate the payment with a GoldFinch customer, order, or invoice.
  3. Store the provider’s transaction reference and status.
  4. Apply the payment to the appropriate transaction.
  5. Reconcile payment activity with settlement or bank information.

Sensitive payment data is handled according to the capabilities and security responsibilities of the applicable payment provider and Salesforce configuration.

Sales-Tax Workflow

A sales-tax integration may:

  1. Send transaction and address information to the tax service.
  2. Receive calculated tax amounts.
  3. Record the tax on the GoldFinch transaction.
  4. Update the tax service when a transaction is committed, adjusted, or canceled.
  5. Support information needed for tax reporting or filing.

The exact workflow depends on the tax provider, jurisdictions, customer configuration, and licensed services.

Accounting Workflow

When GoldFinch ERP connects to an accounting system, it may transfer or post operational transactions based on defined accounting rules.

The workflow may include:

  • Customers and vendors
  • Sales and purchase invoices
  • Credit memos
  • Payments
  • Inventory and cost entries
  • General-ledger entries
  • Account and dimension mappings

During implementation, GoldFinch and the customer determine transaction timing, accounting ownership, mapping rules, posting controls, and reconciliation procedures.

Banking and Expense Workflow

Banking and expense integrations may retrieve or exchange:

  • Bank transactions
  • Corporate-card charges
  • Employee expenses
  • Vendor information
  • Supporting documents
  • Accounting classifications
  • Payment and reconciliation status

Transactions should be reviewed, matched, approved, and posted according to the customer’s configured controls.

Budgeting and Forecasting Workflow

GoldFinch can provide operational and accounting information to compatible planning applications.

For example, GoldFinch can work with CloudBudget, a Salesforce-native budgeting application, to support:

  • Budget preparation
  • Forecasting
  • Department or program budgets
  • Budget-to-actual reporting
  • Analysis using Salesforce records and reporting tools

The planning application remains separately licensed and configured.

Integration Timing

Integrations may operate:

  • In real time when a transaction occurs
  • On a scheduled basis
  • Through an authorized user action
  • Through an approved file import or export
  • Through a combination of these methods

The selected approach depends on transaction volume, API availability, processing requirements, system limitations, and business risk.

Validation and Exception Handling

Don't treat an integration as a one-time technical connection. It requires defined operating controls.

GoldFinch integration planning may address:

  • Required-field validation
  • Duplicate detection
  • Invalid or inactive records
  • Failed transactions
  • Retry procedures
  • User notifications
  • Reconciliation reports
  • Audit history
  • Responsibility for correcting exceptions

Planning an Integration

Before implementation, GoldFinch and the customer should document:

  1. The business objective
  2. The systems involved
  3. The source of truth for each record
  4. The records and fields to be exchanged
  5. Data direction and synchronization timing
  6. Mapping and transformation rules
  7. Security and access requirements
  8. Exception handling and reconciliation
  9. Testing and acceptance criteria
  10. Production support responsibilities

Contact GoldFinch Support or your GoldFinch representative to evaluate a specific integration workflow.

Comments

0 comments

Please sign in to leave a comment.