Skip to main content

Mercury reference

Look up what each status, column, permission and message means on the Mercury page. For how the pieces fit together, see How Mercury works.

Payment statuses​

The Status column of the Payments tab, and the status in the Pay with Mercury dialog while a payment is in progress.

StatusMeansBill or deposit
Awaiting approval in SKU.ioWaiting for someone with Approve payments to approve it on the Payments tabIn progress: it can't be paid again yet
Awaiting Mercury approvalSent to Mercury, waiting for an admin to approve it in Mercury's appIn progress
Approved — processingApproved; Mercury is sending the moneyIn progress
PaidMercury sent it and SKU.io recorded the payment on every bill or deposit it paidPaid or Partially Paid
Not approvedDeclined, in SKU.io or in MercuryPayable again
CancelledCancelled in MercuryPayable again

Under the status, the row says who sent the payment, and once it's reviewed, who approved or declined it and where.

Payments tab​

ColumnShows
IDThe payment's number in SKU.io
SupplierThe supplier paid; links to the supplier
PayingEach bill, purchase invoice or vendor deposit it pays; each links to its page
AmountThe total sent to the supplier
MethodACH, Domestic wire or Check
SentWhen it was sent from SKU.io
StatusSee Payment statuses

Filter by Status, Method and date, and search by supplier, bill or invoice number, or Mercury request ID. Row actions: Approve & send and Decline (while it's awaiting approval in SKU.io), View Supplier, a link to each bill or deposit, and Open in Mercury. Reconcile now asks Mercury for recent payment and approval changes straight away.

Bank transaction matches​

MatchMeans
MatchedLinked to a payment, bill, purchase invoice or vendor deposit. Paid from SKU.io: sent with Pay with Mercury. Auto-matched: an already recorded payment fits on amount and on supplier or reference. Matched by hand: someone confirmed or recorded it, named after "by"
Suggested matchOne or more open bills, deposits or recorded payments fit. Confirm records the top one; with several, you choose
UnmatchedNothing in SKU.io fits
IgnoredMarked as not a supplier payment (Ignored by hand), or Mercury reports the transfer didn't go through

Suggestions come from payments recorded within 10 days of the bank date and from open bills and deposits whose unpaid amount equals the transfer. The reasons shown with each suggestion are: Same amount (or Same as the amount still unpaid), Same supplier, Reference on the transfer, Recorded N days from the bank date and Due within 10 days of the bank date. Up to five suggestions are kept.

Bank transactions tab​

ColumnShows
DateWhen the transaction happened, and the Mercury account
CounterpartyWho Mercury says the money went to or came from, and the matching supplier when SKU.io knows it
DescriptionMercury's bank description and the transfer's note
AmountOutgoing money in red (−), incoming money in green (+)
Bank statusMercury's status for the transfer, for example Sent or Pending
MatchSee Bank transaction matches

Row actions: Confirm match, Record as bill payment… and Record as vendor deposit on a PO… (money out only), Ignore, Restore (ignored rows) and Open in Mercury.

Recipients tab​

ColumnShows
RecipientThe recipient's name in Mercury
EmailThe recipient's email in Mercury
MappingMapped (linked to a supplier) or Unmapped
SupplierThe linked supplier
StatusMercury's status: Active, Invited (waiting for the supplier to add bank details) or Deleted
Payment methodThe recipient's default method in Mercury
Created AtWhen the recipient was first copied into SKU.io

Accounts tab​

Accounts, Total available and Default payment account cards, then each account with its Type (for example Checking) and Available balance. Balances are as of the last connection check; Test connection on the Settings tab refreshes them.

Token permissions​

Test connection on the Settings tab checks each of these with a harmless call. Payment checks use a recipient that doesn't exist, so no money can move.

PermissionUsed for
Read accounts and balancesAccounts tab, default payment account
Read recipientsRecipient sync and supplier mapping
Read transactionsMarking bills paid when Mercury sends the money
Read payment requestsSeeing approvals made in Mercury
Read webhooksInstant payment updates
Send money with approvalPaying bills when approval happens in Mercury
Send moneyPaying bills when approval happens in SKU.io

Each one shows Allowed, Not allowed, Blocked by IP allowlist (the token has the permission, but SKU.io's servers aren't on its allowlist) or Couldn't check. Change permissions on the token in Mercury → Settings → API Tokens.

Webhooks tab​

Webhook Subscription shows whether Mercury sends SKU.io instant updates:

StatusMeans
ActiveMercury sends updates
Paused in MercuryPaused on Mercury's side
Disabled by MercuryMercury stopped sending, usually after repeated failures
Not registeredNo webhook yet; click Register webhook
Can't reach MercurySKU.io couldn't check with Mercury

It also shows the Delivery URL, the Events (transaction created and transaction updated), the Mercury webhook ID, whether a Signing secret is stored, when it was Registered, and the Last event received. Check with Mercury refreshes the status; Register webhook (or Re-register) sets it up again.

Webhook Events lists every update received: Event Type, Resource ID, Status (Received, Processed or Failed), Attempts, Received, Processed and Error. Expand a row to see the full update. Replay Event processes a Received or Failed event again; it needs Integrations → Sync.

Permissions​

To…You need
connect MercuryIntegrations → Create
change Mercury settings, test the connection, register webhooks, link, unlink or invite recipientsIntegrations → Edit
disconnect MercuryIntegrations → Delete
sync recipients, Reconcile now, replay a webhook eventIntegrations → Sync
pay with Mercury, confirm, record, ignore or restore bank transactionsMercury Bill Pay → Send payments
approve payments in SKU.ioMercury Bill Pay → Approve payments
decline a paymentApprove payments, or Send payments for a payment you sent yourself

Alerts​

AlertSent whenSent to
Mercury Payment Awaiting ApprovalSomeone sends a payment that's approved in SKU.ioEveryone who can approve Mercury payments, except the person who sent it
Mercury Payment UpdateA payment is approved and sent, declined (in SKU.io or in Mercury), or fails or is returned by MercuryThe person who sent it

Choose how you get them in Settings → Alerts & Notifications.

Messages​

MessageWhereWhat to do
This bill already has a Mercury payment in progress…Pay with MercuryWait until it's paid or declined, or decline it on the Payments tab
Link [supplier] to a Mercury recipient first.The send buttonLink or invite the supplier in the dialog
More than the open balanceAmountLower the amount
More than your bill payment approval policy approvedAmountRequest approval for the difference first
That account doesn't have enough available balance.The send buttonPick another account or pay less
… is not in USD — Mercury pays USD only.SendingPay it another way
Purchase invoice … is not approved for payment.SendingGet the invoice's payment approved first
Vendor deposit … must be approved before it can be paid.SendingApprove the deposit
Vendor deposit … has payee bank details that haven't been verifiedSendingVerify the deposit's bank details
Payments by … are turned off for this Mercury connectionSendingAllow the method on the Settings tab
This payment is no longer waiting for approval in SKU.io.Approve or declineSomeone else already acted; refresh the list
This is money coming in — only outgoing transfers can be recorded as supplier payments.Bank transactionsIgnore it instead
… has only … left to pay — this transfer is …Bank transactionsPick another document, or record it some other way
Mercury reports this transfer did not go through — there is no payment to record.Bank transactionsNothing to do
This transaction is ignored — restore it first.Bank transactionsClick Restore first
Last verified: