How Transaction Syncing Works
Once your bank account is connected via Plaid, transactions flow into Wired Church automatically. This guide explains the sync schedule, what data comes in, how transactions move through different states, and what to do when something goes wrong.
Automatic Daily Sync
Wired Church syncs transactions from each connected bank account once every 24 hours, typically during the early morning hours (between 2:00 AM and 5:00 AM Central Time).
During each automatic sync:
- Wired Church requests new and updated transactions from Plaid.
- Plaid queries your bank for any transactions that have posted or changed since the last sync.
- New transactions are added to your bank feed with a status of New.
- Previously synced pending transactions are updated if their status or amount has changed.
The exact sync time varies slightly each day and cannot be customized. If you need transactions sooner than the next automatic sync, use the manual sync option described below.
Manual Sync
You can pull the latest transactions on demand at any time:
- Navigate to Finance > Bank Feeds.
- Locate the account card for the bank account you want to sync.
- Click the Sync Now button on the account card.
- A loading indicator appears while Wired Church contacts Plaid.
- New transactions appear in the list within a few seconds.
Use manual sync before starting a reconciliation session or when you know a recent deposit should have posted. There is no limit to how many times you can trigger a manual sync in a day.
What Data Comes In
Each synced transaction includes the following fields from your bank:
| Field | Description | Example |
|---|---|---|
| Date | The transaction date as reported by the bank | 03/12/2026 |
| Description | The merchant name or transaction description | STRIPE TRANSFER 2849301 |
| Amount | The transaction amount (positive for deposits, negative for withdrawals) | +$3,247.50 |
| Type | Debit (withdrawal) or Credit (deposit) | Credit |
| Status | Pending or Posted | Posted |
| Category | Plaid's built-in category (used as a hint by AI categorization) | Transfer |
| Account | Which connected account this transaction belongs to | Operating Checking — Regions |
The description field is whatever your bank provides — it may be a clean merchant name like "Alabama Power" or a cryptic code like "ACH DEBIT 4829103 PAYROLL." The AI categorization engine handles both formats.
Pending vs. Posted Transactions
Banks report transactions in two phases, and Wired Church handles both:
Pending Transactions
- Appear when a charge or deposit is initiated but not yet finalized by the bank.
- Marked with a Pending badge (amber) in the transaction list.
- The amount may change between pending and posted status (common with gas station holds or hotel authorizations).
- Pending transactions are not included in reconciliation totals until they post.
Posted Transactions
- Finalized by the bank — the amount is confirmed and will not change.
- Marked with a Posted badge (green) in the transaction list.
- Included in reconciliation totals and available for categorization and matching.
When a pending transaction posts, Wired Church automatically updates the record:
- If the amount changed, the new amount replaces the old one and a note is added to the transaction history.
- If the transaction was already categorized while pending, the categorization is preserved.
- If a pending transaction disappears (e.g., a hold was released without posting), it is marked as Removed and excluded from all totals.
Avoid categorizing or matching pending transactions for large or variable amounts (like hotel stays or fuel charges). Wait until they post to ensure the final amount is correct.
Transaction States
Every transaction in the bank feed moves through a lifecycle of states. Understanding these states helps you manage your workflow:
New
- The default state when a transaction first syncs.
- Displayed with a blue status badge.
- The transaction has not been reviewed, categorized, or matched.
- New transactions appear in the "Needs Review" count on the Bank Feeds dashboard.
Categorized
- The transaction has been assigned to an account in your chart of accounts, either by AI suggestion or manual selection.
- Displayed with a teal status badge.
- Categorized transactions are ready for reconciliation but have not been matched to an existing internal record.
Matched
- The transaction has been linked to a corresponding record in Wired Church — typically a contribution batch, a payroll entry, or another internal transaction.
- Displayed with a green status badge.
- Matched transactions are considered reconciled.
Excluded
- The transaction has been explicitly marked to be ignored — it will not appear in reconciliation totals or reports.
- Displayed with a gray status badge.
- Common reasons to exclude: bank fee reversals, duplicate entries, internal transfers between your own accounts.
To change a transaction's state:
- Click on the transaction in the list to open its detail panel.
- Use the Status dropdown or action buttons to categorize, match, or exclude.
- Changes save immediately — no separate save button required.
Deposits and Withdrawals
Both sides of your account activity sync through the bank feed:
Deposits (Credits)
- Online giving payouts from Stripe
- Cash and check deposits
- Transfer-in from other accounts
- Interest income
- Insurance reimbursements
Withdrawals (Debits)
- Utility payments
- Payroll
- Vendor payments
- Subscription charges
- Bank fees
- Transfer-out to other accounts
The transaction list can be filtered to show only deposits, only withdrawals, or both. This is useful when you are specifically reviewing income or expenses.
Filtering and Searching Transactions
The bank feed transaction list includes several filtering options to help you find specific transactions:
- Date Range — Set a start and end date to narrow the list. Preset options include This Week, This Month, Last Month, This Quarter, and Custom Range.
- Amount Range — Filter by minimum and/or maximum amount. Useful for finding a specific deposit or isolating large expenses.
- Status — Show only New, Categorized, Matched, or Excluded transactions. Multi-select is supported.
- Account — If you have multiple connected accounts, filter to a single account or view all.
- Search — Free-text search across the transaction description field. Type "Stripe" to find all Stripe payouts, or "Alabama Power" to find utility payments.
When starting your weekly or monthly review, filter by Status: New to see only transactions that need attention. Work through the list, categorizing or matching each one, until the "New" count reaches zero.
Duplicate Detection
Wired Church includes automatic duplicate detection to prevent the same transaction from being counted twice:
- When a sync pulls in a transaction that closely matches an existing record (same date, similar amount, similar description), the system flags it as a Potential Duplicate.
- A warning badge appears on the flagged transaction.
- Click the transaction to see the suspected duplicate side by side.
- You can then choose to Keep Both (if they are genuinely separate transactions) or Exclude One (if it is a true duplicate).
Common scenarios that trigger duplicate detection:
- A transaction syncs as pending and then again as posted (handled automatically in most cases, but occasionally both records persist).
- A manual contribution entry matches a bank deposit for the same amount and date.
- Two very similar vendor charges on the same day (e.g., two Amazon purchases).
Duplicate detection uses a combination of date, amount, and description similarity. It errs on the side of flagging — you may see false positives, especially for recurring charges of the same amount. It is always better to review a false flag than to miss a true duplicate.
Sync History
You can review the history of all sync events for each connected account:
- Navigate to Finance > Bank Feeds.
- Click on the account card to open the account detail view.
- Click the Sync History tab.
- The sync log shows:
- Timestamp — When the sync occurred (automatic syncs show "Scheduled," manual syncs show "Manual").
- Transactions Pulled — How many new or updated transactions were retrieved.
- Status — Success, Partial (some data retrieved but with warnings), or Failed.
- Duration — How long the sync took.
If you notice a gap in sync history (e.g., no successful syncs for several days), your bank connection may need re-authentication. See the troubleshooting section below.
Troubleshooting Sync Issues
Sync Stopped Updating
If your bank feed has not received new transactions in more than 48 hours:
- Check the Sync History tab for recent failures.
- Look for a Connection Error badge on the account card — this means Plaid can no longer authenticate with your bank.
- Click Re-authenticate to go through the Plaid Link flow again. You will not lose any existing transaction data.
- After re-authentication, click Sync Now to pull the latest transactions immediately.
If you ignore a connection error for an extended period, you may have a gap in your transaction history. Plaid typically provides up to 90 days of backfill on reconnection, but this varies by bank. Reconnect as soon as you notice the error.
Transactions Missing
If you know a transaction has posted at your bank but it does not appear in Wired Church:
- Confirm the transaction shows as "Posted" (not just "Pending") in your bank's online portal.
- Click Sync Now to trigger an immediate sync.
- Wait 2-3 minutes and refresh the page.
- If the transaction still does not appear, check whether it falls within the date range of your current filter view.
- If the issue persists after 24 hours, the transaction may be in a category that Plaid does not report (rare). Contact support at help@wiredchurch.com with the transaction details.
Incorrect Transaction Amounts
In rare cases, a transaction amount may differ between your bank statement and the bank feed:
- This most commonly happens with pending transactions that changed amounts before posting.
- Wait for the transaction to show as "Posted" — the amount should update automatically on the next sync.
- If a posted transaction shows the wrong amount, contact support — this may indicate a Plaid data issue that needs to be reported to your bank.
Frequently Asked Questions
How far back does the initial sync go? Typically 30 to 90 days, depending on your bank. Some banks provide up to 24 months of history. After the initial sync, all future transactions are captured daily.
Does syncing cost extra? No. Transaction syncing is included with your Pro or Enterprise subscription at no additional cost.
Can I sync transactions from a closed account? No. Once a bank account is closed, the Plaid connection will fail. However, all previously synced transactions remain in the system and are fully accessible.
What if my bank has an outage? If your bank is temporarily unavailable, the scheduled sync will fail and retry on the next cycle. Plaid handles temporary bank outages gracefully — no action is needed on your part.
Are weekend transactions synced? Yes. Automatic syncs run every day, including weekends and holidays. However, some banks do not post transactions on weekends, so you may see a batch of new transactions appear on Monday morning.