Consider a hypothetical landscaping contractor who sends a customer an invoice for $1,000 and receives a card payment for the full amount. Two business days later, the bank deposit arrives for $971.00. The processor has taken its charge before the money reached the account, and the difference appears on a statement line that the owner, occupied with crews and equipment, may never open.
The gap usually surfaces at the wrong moment, when a bookkeeper reconciles the month, finds that the sales ledger and the bank statement disagree, and asks where the rest went. By then the question is larger than one invoice. It concerns whether every card receipt was recorded at gross and matched to a net deposit, and whether the processing fees were booked as an expense or quietly netted against revenue. Those are different entries, and they describe different businesses.
Card fees are neither hidden nor mysterious. They are the cost of accepting cards, and the processor reports them on each statement, typically as a percentage of the sale plus a fixed amount per transaction. Rates vary by provider and by plan, so the figure on one statement belongs to that account alone. EEZYPAY publishes its pricing on its site. The useful work is modest: read the statement once, identify which lines are fees, and record gross sales and fees as separate entries so each deposit can be traced to its invoice. An owner who does that does not need to become a bookkeeper.
A card payment rarely arrives at its invoiced amount, and the gap is not necessarily an error. It reflects the difference between gross and net. The gross figure is what the customer paid. The net figure is what the processor deposits after deducting its charges. Most owners see only the net, on a bank statement that gives no context for the difference.
Card processing fees usually combine a percentage of the transaction with a fixed amount per transaction. The percentage scales with the invoice, while the fixed amount weighs more heavily on small payments. Either way, the processor takes its charge before it remits the balance.
Other items can reduce the same settlement. A refund returns money to the customer and may or may not return the original processing fee, depending on the provider. A chargeback, which occurs when a cardholder disputes a charge through the issuing bank, removes the disputed amount and often carries a separate fee, whether or not the company wins. Each line reduces the deposit independently of the invoice that produced it.
Consider a consultant who invoices a client $1,000 on net-30 terms, and the client pays by card. Illustratively, the processor charges $31.00, so the deposit is $969.00. Later, the client disputes a separate $150 charge, and the bank removes $150 plus an illustrative $15.00 dispute fee. The bookkeeper, reconciling the account, finds a $969.00 deposit against a $1,000 invoice and a $165.00 debit that matches no invoice on the list. Neither item is an error. Each must be recorded against its source.
Reconciliation therefore runs in a fixed order. The bookkeeper matches each deposit to the gross amounts of the invoices it settles, then records fees and disputes as separate expenses or adjustments. Providers such as Stripe Invoicing, Square Invoices, QuickBooks Payments and PayPal Invoicing generally issue payout or settlement reports that itemize these components. An owner who requests that report before the bookkeeper asks will usually find the gap explained in minutes.
A card payment passes through several parties, and each takes a share. The card network sets the rules for the transaction and levies its own assessment. The issuing bank, which provided the cardholder’s card, receives the interchange fee, usually the largest component. The acquiring processor holds the merchant account, adds its own markup and settles the funds to the business. A software provider that sits on top of the processor may add a charge of its own. The deposit is the invoice amount less the sum of these layers.
Fees vary because the risk and cost differ from one transaction to the next. Premium and rewards cards carry higher interchange than standard debit cards. A card that the customer presents at a terminal costs less to accept than one entered by hand or paid online, since the card-not-present transaction carries more fraud exposure. Cards issued abroad cost more to process, and a payment initiated through an emailed link may price differently from a card tapped at a counter. The same invoice can settle at different amounts depending on which card the customer happens to use.
For this reason, a single advertised rate rarely describes the effective cost. The effective rate is total fees divided by total card volume over a period, and it depends on the mix of cards a business accepts. A consulting firm whose clients pay mostly on commercial cards will experience a different effective rate from a contractor whose customers pay mostly by debit. The owner who compares rates should compare them on the same mix of transactions.
The limits of any fee schedule deserve plain statement. A processor’s published schedule does not capture every charge a business may face. Monthly minimums, chargeback fees, currency conversion and account-level fees can appear on separate lines. Rules on surcharging, the practice of passing the card fee to the customer, and on cash discounts depend on state law and card network rules. Some states prohibit surcharges, some require advance notice, and network rules set their own disclosure and caps. The business should confirm these requirements locally with its processor and, where the answer carries financial or legal weight, with counsel.
EEZYPAY provides invoicing, payment links and card payment processing for small businesses, and payments settle through Stripe. The sequence below follows a single card payment from the moment a company bills a customer to the moment the funds arrive.
The net amount is the figure to reconcile. The invoice total and the deposit will differ, and the difference should appear as a processing charge on the statement. Match that line against the invoice before closing the month, not after a bookkeeper raises it. Pricing is on the EEZYPAY site. Read the fee terms there before setting customer prices, so that the fee comes out of a margin the company set aside for the purpose.
Owners comparing options will also find Stripe Invoicing, Square Invoices, QuickBooks Payments, PayPal Invoicing, Bill.com and Melio. Each one invoices or accepts payments in its own way, and each publishes its own fee schedule. Compare the schedules themselves rather than summaries of them.
Questions about service availability belong at https://eezycloud.com/uptime/.
EEZYPAY publishes its pricing at https://eezypay.net. This section gives no figures, because none appear in the company’s stated facts, and the site is the authoritative source. The button on the site reads “Get Started,” and nothing in its pricing is free. Any comparison should therefore start from the published schedule and the processor’s written terms. The method below applies to any processor, including Stripe Invoicing, Square Invoices, QuickBooks Payments, Bill.com, Melio and PayPal Invoicing.
Ask for the all-in effective rate before weighing a headline percentage. A quoted rate plus a per-transaction charge seldom describes what an account costs. Divide a month’s total fees by that month’s total card volume. The result is the figure to compare across providers.
Then request the following in writing:
Pull three recent months of card volume before deciding. Record the transaction count, the average payment, the refund count and the dispute count. Run each candidate’s published or quoted terms against those three months. A provider that appears inexpensive per payment can cost more once refunds and monthly fees enter the calculation. A firm that bills large invoices and rarely refunds will weigh these items differently from a firm that handles many small payments.
Finally, reconcile the net deposit against the invoice. The difference should match the fees on the statement, and each fee should carry a name. If a bookkeeper cannot match a deposit to an invoice without assistance, the account needs a clearer report before it needs a lower rate.
Consider a two-person agency that sets up its first payment link on a Monday. The owner begins with the business profile: the legal name, the tax identification number, the business address, and the owner’s personal details. The processor must confirm who controls the account, so the entries should match the company’s tax filings exactly. The agency’s bookkeeper should pull those documents before the owner starts, not during.
Card payments settle through Stripe, which requires identity and bank verification before it releases funds. The owner should expect questions about identity and a confirmation step for the bank account. Verification controls when money can move, so an incomplete profile delays the first deposit more than any other step.
Next, the owner connects the account that receives payouts. This should be the operating account the bookkeeper reconciles each month, not a personal account. The owner enters the routing and account numbers and checks them against a bank statement. Mapping the account now means the deposits land where the person reviewing them will look.
Before any real invoice goes out, the owner tests one. The agency sends an invoice to an address it controls, pays it with a card the owner holds, and compares the amount received with the invoice total. The difference is the processing fee, and it should appear in the payout record. Recording that figure at the start gives the bookkeeper a reference point for every deposit that follows.
If a step stalls, support runs at https://eezycloud.com/support, Monday through Friday 9 AM to 8 PM and Saturday and Sunday 9 AM to 12 PM Eastern. Owners comparing onboarding should look at Stripe Invoicing, Square Invoices, QuickBooks Payments, Bill.com, Melio, and PayPal Invoicing, since each runs its own verification sequence. Pricing for EEZYPAY is on the site.
Several established tools accept card payments on invoices, and each suits a different kind of business. The descriptions below name no prices or fees, because those vary by plan, country and payment method. Each provider’s own pricing page is the place to check the deduction on a sample invoice.
Stripe Invoicing suits businesses with a developer on staff, or with the willingness to configure an API-based tool, that want invoicing built into a larger payments system. Square Invoices suits businesses that already run Square point-of-sale hardware, since invoices and card readers share one account. QuickBooks Payments suits businesses that keep their books in QuickBooks and want payments recorded against invoices without a separate import. Bill.com suits firms with substantial volumes of both incoming and outgoing invoices, where approval chains and accounts payable workflows matter more than the cost of a single card transaction. Melio suits businesses that both pay and receive money from other businesses, often by bank transfer as well as by card. PayPal Invoicing suits businesses whose customers already hold PayPal accounts and expect to pay that way.
Two questions separate these options more reliably than feature lists. The first is where the books live. A tool that posts payments to the ledger without manual matching saves more time than one with a lower card rate that leaves reconciliation to a bookkeeper. The second is how the customer prefers to pay. A method that requires the customer to create an account adds friction, and friction delays payment, which is the cost this subject concerns.
EEZYPAY is one option in this group. It offers invoicing, payment links and card processing for small businesses, settled through Stripe, and its pricing appears on the site. The comparison that matters is the one the reader runs: the net amount that reaches the bank on a typical invoice, weighed against the tool’s cost, the hours spent matching payments, and the speed of collection. Ask each provider for a written statement of the deduction on a sample transaction. A provider that answers plainly has made the comparison easy, and one that does not has told you something as well.
A card payment passes through three records before it reaches the books. The invoice creates a receivable in the accounting software. The processor settles the payment as a single net deposit into the bank account. The bank feed then shows that deposit as a line the bookkeeper must match. The difference between the invoice and the deposit is the processing fee, and it belongs in an expense account. When the fee is netted silently, the receivable never clears cleanly, and the bookkeeper spends the close hunting for the gap.
Three checks prevent most of that work. First, confirm that the processor’s payout record lists the gross amount, the fees, and any refunds or disputes as separate lines, so the bookkeeper can split the deposit without guessing. Second, confirm that each payment carries the invoice number through to the payout, so matching runs on identifiers rather than amounts. Third, decide which account receives the fees before the first payout arrives. A company that settles this in advance spends one afternoon on setup. A company that settles it during the close spends several.
EEZYPAY is one product in the EEZYVERSE family. One login covers every EEZY product a company uses, and each product is also sold on its own site, so a firm that needs only invoicing and payment links can buy that alone. A company that runs several EEZY products pays through one central bill at https://eezycloud.com/account/, which gives the bookkeeper one place to reconcile those charges against the ledger.
Stripe Invoicing, Square Invoices, QuickBooks Payments, Bill.com, Melio and PayPal Invoicing each draw this boundary in a different place. The test is the same for every one of them: run a single month’s close against a sample of card payments and count the manual corrections. The number that matters is not the fee rate. It is the number of deposits that cannot be matched without someone opening the payout report.
The point to make to a colleague is simple. Agree on the matching rule, the fee account and the reference format before the first card payment settles. An unexplained difference in week one is an irritation. The same difference in month twelve is a reconciliation problem.
A card fee usually combines three parts: interchange, set by the card networks and paid to the issuing bank; assessments, charged by the networks themselves; and a processor markup. The processor's share is the part a business can compare across providers. EEZYPAY pricing is published on its site.
An advertised flat rate often omits surcharges that apply to certain cards, such as premium rewards or corporate cards, and to keyed-in transactions without a card present. The effective rate is total fees divided by total card volume. A business should compute that figure from its own statements before comparing providers.
The business pays the fee by default. Some providers allow a surcharge passed to the customer, but card networks set conditions on surcharging, and rules vary by state and by card type. A business that surcharges should confirm the rules that apply before it adds a line item to an invoice.
EEZYPAY card payments settle through Stripe. Payout timing follows the settlement terms, so a business should read them before it plans payroll or supplier payments against expected card receipts. Pricing for the fees themselves is on the EEZYPAY site.
A business can offer bank transfer or check alongside cards, and large invoices often make that split worthwhile. Each method carries different costs and settlement timing, so the choice turns on how the business weighs speed against fees. EEZYPAY offers invoicing, payment links and card processing, with pricing on its site.
EEZYPAY handles invoicing, payment links and card processing for small businesses, with payments settled through Stripe. Pricing is on the site at https://eezypay.net.
EEZYPAY is part of the EEZYVERSE family: one login, one bill, every EEZY product.
Choose which cookies you allow. Essential cookies are always active because they are required for the site to function.