Overview

AcctSeed.BDCMatchStrategy is a global Apex interface that lets you plug custom bank-transaction matching logic into the Accounting Seed BDC automated match pipeline. You register your implementation through an AcctSeed__Binding__mdt custom metadata record; the platform discovers and executes it as part of the normal bank transaction processing workflow.

 

The Interface

global interface AcctSeed.BDCMatchStrategy {
    List<AcctSeed.BDCMatchCandidate> suggestMatches(List<AcctSeed__Bank_Transaction__c> bankTransactions);
}
suggestMatches is called with a batch of AcctSeed__Bank_Transaction__c records and must return a flat list of match candidates. An empty list signals that no matches were found for any record in the batch.

The method receives a List — not a single record — to support bulk patterns. If your matching logic calls an external API, you can process all records in a single call rather than one call per transaction.

 

Implementing the Interface

global class MyCustomMatchStrategy implements AcctSeed.BDCMatchStrategy {
    global List<AcctSeed.BDCMatchCandidate> suggestMatches(List<AcctSeed__Bank_Transaction__c> bankTransactions) {
        List<AcctSeed.BDCMatchCandidate> candidates = new List<AcctSeed.BDCMatchCandidate>();
        for (AcctSeed__Bank_Transaction__c bt : bankTransactions) {
            // Query for potential source documents using your matching logic
            for (AcctSeed__Bank_Deposit__c bd : findCandidates(bt)) {
                candidates.add(
                    new AcctSeed.BDCMatchCandidate(bt.Id, bd)
                        .withConfidence(0.85, 'Matched by vendor name similarity')
                );
            }
        }
        return candidates;
    }
    private List<AcctSeed__Bank_Deposit__c> findCandidates(AcctSeed__Bank_Transaction__c bt) {
        // Your logic here
        return new List<AcctSeed__Bank_Deposit__c>();
    }
}

Implementation rules:

Each AcctSeed.BDCMatchCandidate carries its own bankTransactionId, so a single flat list covers all input records.

The implementation class must be global to be resolvable by the platform when referenced from a managed package context.

 

BDCMatchCandidate

AcctSeed.BDCMatchCandidate is a global class representing a single potential match between a bank transaction and a source document.

Constructors:

// From an SObject — extracts Id and SObjectType automatically (preferred)
new AcctSeed.BDCMatchCandidate(Id bankTransactionId, SObject matchedRecord)
// From explicit IDs when you only have identifiers
new AcctSeed.BDCMatchCandidate(Id bankTransactionId, Id matchedRecordId, Schema.SObjectType matchedRecordType)

All three parameters are required and validated — passing null for any throws IllegalArgumentException.

Fields:

Field	Type	Required	Description
bankTransactionId	Id	Yes	The AcctSeed__Bank_Transaction__c this candidate is for
matchedRecordId	Id	Yes	Id of the source document
matchedRecordType	Schema.SObjectType	Yes	SObject type of the source document
confidenceScore	Decimal	No	0.0–1.0; 1.0 = exact match, lower = fuzzy. Reserved for future use — not currently evaluated by the platform.
matchReason	String	No	Human-readable explanation of the match. Reserved for future use — not currently displayed by the platform.

Fluent setter:

candidate.withConfidence(0.90, 'Amount within 2% tolerance');
Returns this for chaining.

Supported source document types:

Your matchedRecordType must be one of the following. Candidates for any other type are automatically discarded:

• AcctSeed__Cash_Receipt__c
• AcctSeed__Cash_Disbursement__c
• AcctSeed__Bank_Deposit__c
• AcctSeed__Bank_Disbursement__c
• AcctSeed__Journal_Entry_Line__c

 

What the Platform Does Automatically

After suggestMatches() returns, the platform applies several safeguards before acting on your candidates. You do not need to implement these yourself, but your implementation should be aware of them:

Date-window filtering: Candidates whose source document date falls outside a configurable tolerance window around the bank transaction's date are silently dropped. The window is driven by the Cash-In and Cash-Out matching settings configured in Accounting Settings. Returning candidates that are likely outside the window is harmless but wasteful.

Already-matched guard: Source documents already linked to another bank transaction are automatically excluded.

GL Account Mapping (GLAM) validation: Candidates are dropped if the source document's ledger or GL account does not align with the bank transaction's GL Account Mapping.

1:1 auto-accept: If auto-matching is enabled. A bank transaction that has exactly one candidate (and that candidate maps to no other bank transaction) is automatically accepted and its status set to Matched.

Ambiguous deferral: If a bank transaction has multiple candidates, it is held in a deferred state so a subsequent strategy (with a higher AcctSeed__Order__c value) can attempt to resolve it. Bank transactions that remain ambiguous after all strategies have run are rejected for human review rather than auto-matched.

 

Registering via AcctSeed__Binding__mdt

Each strategy requires one AcctSeed__Binding__mdt record. The platform discovers all active records where AcctSeed__Type__c = 'BDCMatchStrategy' and runs them in ascending AcctSeed__Order__c order, each as a separate batch job.

Field reference:

Field	API Name	Required	Description
Label	(record label)	Yes	Human-readable name for this binding
Type	AcctSeed__Type__c	Yes	Must be exactly BDCMatchStrategy
To	AcctSeed__To__c	Yes	Fully-qualified Apex class name of your implementation
Is Active	AcctSeed__Is_Active__c	—	Set to true for the strategy to participate. Defaults to false.
Order	AcctSeed__Order__c	—	Execution sequence (ascending). Lower numbers run first. The built-in exact amount strategy uses 10; use a higher value to run after it or lower to run before.
Batch Size	AcctSeed__Batch_Size__c	—	How many AcctSeed__Bank_Transaction__c records are passed to suggestMatches() per call. Valid range: 1–2000. Defaults to 200.
Namespace	AcctSeed__Namespace__c	—	Namespace prefix of your Apex class. Leave blank for unmanaged classes.
Description	AcctSeed__Description__c	—	Free-text documentation field.

Example metadata file (force-app/main/default/customMetadata/AcctSeed__Binding.MyCustomMatch.md-meta.xml):

<?xml version="1.0" encoding="UTF-8"?>
<CustomMetadata xmlns="http://soap.sforce.com/2006/04/metadata"
                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <label>My Custom Match</label>
    <protected>false</protected>
    <values>
        <field>AcctSeed__Type__c</field>
        <value xsi:type="xsd:string">BDCMatchStrategy</value>
    </values>
    <values>
        <field>AcctSeed__To__c</field>
        <value xsi:type="xsd:string">MyCustomMatchStrategy</value>
    </values>
    <values>
        <field>AcctSeed__Is_Active__c</field>
        <value xsi:type="xsd:boolean">true</value>
    </values>
    <values>
        <field>AcctSeed__Order__c</field>
        <value xsi:type="xsd:double">20</value>
    </values>
    <values>
        <field>AcctSeed__Batch_Size__c</field>
        <value xsi:type="xsd:double">50</value>
    </values>
    <values>
        <field>AcctSeed__Namespace__c</field>
        <value xsi:type="xsd:string"></value>
    </values>
    <values>
        <field>AcctSeed__Description__c</field>
        <value xsi:type="xsd:string">Matches by vendor name similarity after exact amount strategy.</value>
    </values>
</CustomMetadata>

Set AcctSeed__Is_Active__c to false on the binding record to disable a strategy without deleting it.

---