Reconciling Paystack Against Your Bank Statement

You have two layers of reconciliation before this one. The daily reconciliation job confirms your ledger matches Paystack. The settlement reconciliation confirms which transactions Paystack settled. But neither confirms the money actually arrived in your bank.

Bank reconciliation closes the loop. It answers: "For every settlement Paystack says they sent, did a matching deposit actually appear in our bank account?" This catches:

• Bank processing errors where a deposit was lost or misrouted.
• Paystack settlement errors where the amount deposited differs from the settlement record.
• Unexpected deposits that do not correspond to any Paystack settlement (could be refunds, transfers from other sources, or errors).
• Missing deposits where Paystack shows a settlement but your bank has no record of receiving it.

Most Nigerian and African banks offer statement downloads in CSV, Excel, or PDF format. CSV is the easiest to parse programmatically. If your bank only provides PDF statements, you will need a PDF parsing step (or switch to CSV export if available).

For some banks, you can also access statement data through banking APIs or open banking platforms. This is the ideal approach for automation but depends on your bank and country.

// Parse a bank statement CSV
var fs = require('fs');

function parseBankStatement(filePath) {
  var content = fs.readFileSync(filePath, 'utf-8');
  var lines = content.split('
');

  // Skip header row
  var header = lines[0].split(',');

  // Find column indices (these vary by bank)
  var dateCol = header.indexOf('Date') !== -1 ? header.indexOf('Date') : 0;
  var creditCol = header.indexOf('Credit') !== -1 ? header.indexOf('Credit') : header.indexOf('Deposit');
  var descCol = header.indexOf('Description') !== -1 ? header.indexOf('Description') : header.indexOf('Narration');

  var deposits = [];

  for (var i = 1; i < lines.length; i++) {
    var cols = lines[i].split(',');
    if (cols.length < 3) continue;

    var creditStr = cols[creditCol] ? cols[creditCol].replace(/[^0-9.]/g, '') : '';
    var creditAmount = parseFloat(creditStr);

    if (creditAmount > 0) {
      deposits.push({
        date: new Date(cols[dateCol].trim()),
        amount: Math.round(creditAmount * 100), // Convert to kobo
        description: cols[descCol] ? cols[descCol].trim() : '',
        raw_line: lines[i],
      });
    }
  }

  return deposits;
}

Column names and date formats vary by bank. You will need to adjust the parsing logic for your specific bank's CSV format. Test with a real statement before relying on the parser.

Match bank deposits against your settlement records. The match criteria are: amount matches exactly (or within a small tolerance) and the date is within a few business days of the settlement date.

// Match bank deposits against settlements
async function reconcileBankStatement(deposits) {
  // Fetch recent settlements from our records
  var settlements = await db.query(
    'SELECT id, total_amount, currency, settled_date, paystack_settlement_id '
    + 'FROM settlements '
    + 'WHERE settled_date >= NOW() - INTERVAL '45 days' '
    + 'AND bank_matched = false '
    + 'ORDER BY settled_date'
  );

  var results = {
    matched: [],
    unmatched_deposits: [],
    unmatched_settlements: [],
  };

  var settlementList = settlements.rows.slice();

  for (var i = 0; i < deposits.length; i++) {
    var deposit = deposits[i];
    var matched = false;

    for (var j = 0; j < settlementList.length; j++) {
      var settlement = settlementList[j];

      // Amount match (allow small tolerance for bank rounding)
      var amountDiff = Math.abs(deposit.amount - settlement.total_amount);
      if (amountDiff > 100) continue;  // More than 1 naira difference

      // Date match (allow 3 business days)
      var daysDiff = Math.abs(deposit.date - new Date(settlement.settled_date));
      var businessDays = daysDiff / (24 * 60 * 60 * 1000);
      if (businessDays > 5) continue;  // Allow up to 5 calendar days (3 business)

      // Match found
      results.matched.push({
        deposit: deposit,
        settlement: settlement,
        amount_diff: amountDiff,
        days_diff: Math.round(businessDays),
      });

      // Mark settlement as matched
      await db.query(
        'UPDATE settlements SET bank_matched = true, bank_match_date = $1 WHERE id = $2',
        [deposit.date, settlement.id]
      );

      settlementList.splice(j, 1);
      matched = true;
      break;
    }

    if (!matched) {
      // Check if the description mentions Paystack
      var isPaystack = deposit.description.toLowerCase().indexOf('paystack') !== -1;
      results.unmatched_deposits.push({
        deposit: deposit,
        likely_paystack: isPaystack,
      });
    }
  }

  // Remaining unmatched settlements
  results.unmatched_settlements = settlementList;

  return results;
}

Timing differences. A settlement processed on Friday may not appear in your bank until Monday or Tuesday. Weekend and public holiday delays are the most common reason for apparent mismatches. Widen your date tolerance window and re-check after a few business days before escalating.

Bank fees. Some banks charge fees for receiving deposits. If Paystack sends NGN 4,925,000 but your bank charges a NGN 500 incoming transfer fee, the deposit shows as NGN 4,924,500. Set a tolerance in your matching algorithm to account for this. Track these bank fees separately for expense reporting.

Consolidated deposits. Some banks or Paystack configurations may combine multiple settlements into a single bank deposit. If your bank shows one deposit of NGN 9,850,000 but you have two settlements of NGN 4,925,000 each, your matching algorithm needs to handle this. One approach: if an unmatched deposit equals the sum of two unmatched settlements with similar dates, flag it as a potential consolidation for manual review.

Different description formats. The bank statement description might say "PAYSTACK SETTLEMENT" or "PS/BATCH/12345" or just a generic transfer reference. Map known description patterns to Paystack settlements. If the description contains a batch ID, cross-reference it with the Paystack settlement ID.

Refund deductions. Paystack may deduct refunds from settlement amounts. A settlement of NGN 4,925,000 minus a NGN 50,000 refund results in a deposit of NGN 4,875,000. Your matching should check for refund deductions when the deposit is slightly less than the settlement. See the refund accounting guide for more detail.

// Generate investigation report for unmatched items
async function generateInvestigationReport(results) {
  var report = 'Bank Reconciliation Investigation Report

';

  if (results.unmatched_deposits.length > 0) {
    report += 'UNMATCHED BANK DEPOSITS (money in bank, no settlement match):
';
    for (var i = 0; i < results.unmatched_deposits.length; i++) {
      var d = results.unmatched_deposits[i];
      report += '  ' + d.deposit.date.toISOString().split('T')[0]
        + '  ' + formatCurrency(d.deposit.amount, 'NGN')
        + '  ' + d.deposit.description
        + (d.likely_paystack ? '  [LIKELY PAYSTACK]' : '') + '
';
    }
    report += '
';
  }

  if (results.unmatched_settlements.length > 0) {
    report += 'UNMATCHED SETTLEMENTS (settlement recorded, no bank deposit):
';
    for (var j = 0; j < results.unmatched_settlements.length; j++) {
      var s = results.unmatched_settlements[j];
      var age = Math.round((Date.now() - new Date(s.settled_date)) / 86400000);
      report += '  ' + s.settled_date
        + '  ' + formatCurrency(s.total_amount, s.currency)
        + '  Paystack ID: ' + s.paystack_settlement_id
        + '  Age: ' + age + ' days'
        + (age > 5 ? '  [INVESTIGATE]' : '  [MAY BE IN TRANSIT]') + '
';
    }
    report += '
';
  }

  report += 'MATCHED: ' + results.matched.length + '
';
  report += 'UNMATCHED DEPOSITS: ' + results.unmatched_deposits.length + '
';
  report += 'UNMATCHED SETTLEMENTS: ' + results.unmatched_settlements.length + '
';

  return report;
}

For unmatched settlements older than 5 business days, contact Paystack support with the settlement ID and ask for the payment reference or proof of deposit. For unmatched bank deposits that mention Paystack, check whether they correspond to a settlement from a different date range than you searched.

Full automation of bank reconciliation is difficult because bank statement formats are inconsistent and many banks do not offer API access. A practical approach:

• Automate parsing: Build a parser for your bank's specific CSV format. This saves the most time.
• Automate matching: The matching algorithm handles the straightforward cases (exact amount, close date).
• Manual review for edge cases: Consolidated deposits, amount mismatches, and old unmatched items need human judgment.
• Automate reporting: Generate the investigation report automatically and email it to your finance team.

If your bank offers an API (some Nigerian fintech banks do, as do some traditional banks through open banking), you can fully automate the statement download and eliminate the manual CSV step entirely.

For Kenyan businesses that receive Paystack settlements via M-Pesa, see the M-Pesa reconciliation guide which covers a similar process with M-Pesa-specific details.

Bank reconciliation has a natural cadence:

• Weekly: Good for businesses processing 100+ transactions per day. Catches issues while they are fresh and easy to investigate.
• Monthly: The minimum recommended frequency. Aligns with month-end close procedures. See the month-end close guide.
• Ad hoc: Run whenever you notice unexpected bank balance changes or when preparing for financial audits.

Schedule it after your Paystack settlement data is complete for the period. If you reconcile the first week of August, your July settlements should all be finalized. Allow a few extra business days for the last settlement of the month to arrive in your bank.