Getting paid in is only one part of getting paid for your work. You still need a clear invoice, a way to match the receipt to the job, and records of what happened between receiving LTC and receiving money in your bank. A cheap network transfer can be followed by an expensive conversion.
Start with the commercial agreement: what the client owes, in which currency, by when, and what happens if the amount or timing is wrong. Then choose the payment route. The examples below are fictional calculations, not current provider quotes or personal tax advice.
Agree the price and the conversion rule
A $1,000 service invoice can offer a Litecoin payment option while keeping the debt denominated in dollars. That is different from agreeing that the work costs 20 LTC regardless of its later dollar value. Write down which arrangement you mean.
For a -priced invoice, record the conversion source, the time of the quote, the LTC amount requested and the expiry rule. The currency calculator can provide reference arithmetic. It does not bind an or payment processor to execute at that rate. If someone promises a rate lock, check who is making that promise and which conditions end it.
An expired quote does not cancel a Litecoin transaction or return the coins. It creates a reconciliation question: what arrived, when did it arrive, and what do your agreed terms say? The invoice clock simulator separates an invoice deadline from broadcast, observation, and acceptance.
A payment request is not the whole legal invoice
Your , QR code and LTC amount are payment instructions. They do not replace the invoice details required where your business operates. For example, the UK government's invoice checklist includes a unique number, supplier and customer details, a description, supply and invoice dates, amounts, and VAT where applicable. Sole traders and companies have additional requirements. Official UK invoice requirements.
| Record | Decision it supports |
|---|---|
| Invoice ID, client and service reference | Which debt is being settled? |
| Price, tax treatment and currency of the debt | What does the client owe before choosing a payment method? |
| Requested LTC, quote source, timestamp and expiry | Which conversion did both sides accept? |
| Verified native Litecoin destination | Where must the payment arrive? |
| Required recipient amount and confirmation policy | When will you treat the invoice as accepted? |
| Rules for short, excess, late and duplicate payments | What happens when the receipt differs from the request? |
| Refund denomination and authenticated return instructions | How is a refund calculated and where can it safely be sent? |
Use a fresh receiving address where your supports it, and check the full address on a trusted wallet display before sending the instructions. Fresh addresses reduce direct reuse; they do not guarantee that transactions are unlinkable. Keep the invoice-to-address mapping in your own records.
Do not rely on a wallet's payment-note field to carry the invoice reference to you. Put the reference in the invoice and keep the correspondence. Our payment-note tests explain why a note shown by the sender can be separate from the received transfer.
Separate the sender's fee from the amount you receive
If the agreed recipient amount is 20 LTC, the client's final wallet preview should show 20 LTC going to your destination. A paid on top does not reduce that output. A wallet option that subtracts the fee from the recipient amount can leave you short, even if the sender's total debit looks right.
Your later transfer to a conversion service is a different event. That fee can reduce the quantity you sell. Keep the invoice receipt, the transfer to the service and the bank payout as separate records rather than calling all three amounts “the payment.” See exact amounts, fee subtraction and send max.
A worked route from a $1,000 invoice to the bank
Assume the invoice has no additional sales tax or VAT in this example, and the agreed quote is $50 per LTC. The client sends the requested 20 LTC and pays their network fee separately. You receive 20 LTC. You then pay a fictional 0.001 LTC transfer fee from those coins, so the service receives 19.999 LTC to sell.
The service's assumed is 0.5% of the sale proceeds, followed by a $2 fiat . There is no extra spread or currency conversion in this deliberately bounded example. Real quotes can include both, as well as limits and additional charges.
| Route | Quantity and execution assumption | Bank receipt before tax |
|---|---|---|
| Fiat processor | $1,000 less an assumed 3% charge; no other costs | $970.00 |
| LTC, unchanged sale price | 19.999 LTC sold at $50; 0.5% trading fee and $2 withdrawal | $992.95 |
| LTC, sale price 2% lower | 19.999 LTC sold at $49; the same fee rule and withdrawal charge | $973.05 |
The unchanged-price row is 19.999 × 50 × (1 − 0.005) − 2 = 992.95025. The lower-price row is 19.999 × 49 × (1 − 0.005) − 2 = 973.051245. Displayed receipts are rounded to cents at the end; a provider's own rounding can differ. The earlier receipt of 20 LTC remains the same in both rows. The later selling price changes.
Download the calculation ledger · CSV · Assumptions and reproduction. The native transfer fee is charged once on the freelancer's outgoing leg. The client's separate fee is not deducted again from the invoice receipt.
Check acceptance before delivering more work
Use your receiving wallet or an independently checked payment backend. A client's screenshot is not a receipt. Match the actual destination and recipient amount to the invoice, then apply your confirmation and fulfillment policy. The transaction checker inspects the public network record; it cannot see an exchange account's internal credit decision.
Our payment workbench helps prepare requests and reconcile supplied invoice and receipt records. It does not connect to your wallet, approve a payment or make a legal invoice for your jurisdiction. Keep an order open when the evidence is incomplete rather than automatically asking the client to pay again.
Native Litecoin does not have the same reversal process as a card payment. That does not remove contractual refund duties or legal remedies, and confirmation is not an absolute finality guarantee. Agree the acceptance policy before a dispute.
Choose software and conversion as separate services
BTCPay lists Litecoin as an opt-in integration maintained by the community; its core project's focus is Bitcoin. A listing is not a promise that your current hosted instance supports LTC, every wallet feature or a bank payout. Confirm the actual deployment, maintainer and supported payment path. BTCPay's altcoin documentation.
Self-hosted invoice software is not automatically an exchange or fiat settlement provider. Establish where the LTC is held, who can sign, which service converts it and what the withdrawal terms are. Test the intended invoice-to-bank route with a bounded amount before offering it as a routine client workflow. Do not promise a bank-settlement time based only on a Litecoin target.
Keep tax evidence for receipt and later disposal
The US IRS FAQ says digital assets received for services create ordinary income measured at dollar fair market value when received. For an independent contractor, that value generally constitutes self-employment income. Where that value is included in income, it also establishes the basis described in the FAQ. The taxpayer's circumstances and accounting rules still matter. A block time or invoice quote alone is not a complete tax method. IRS digital-asset FAQ, questions 57–60.
In a separate, fee-free example, 10 LTC received for work at $60 each has a $600 receipt value. A later $650 sale has a $50 difference before applicable costs and tax rules. The entire $650 is not a second $650 investment profit. The cash-route table above should not be pasted into a tax return as a tax-gain calculation.
For a UK example, HMRC requires appropriate transaction-time conversion into sterling and records of a consistent valuation methodology; accounting and tax rules determine the treatment. That is a different task from converting only the final bank payout. US and UK examples do not establish the rules in another country. HMRC on conversion and accountancy.
Keep the legal invoice, exact LTC units, relevant event times, valuation evidence, transaction references, fees, sale confirmations and bank receipt. Identify which transfer belongs to which invoice. Back up those records separately from the wallet material needed to sign. The records backup guide covers exports and restoration checks.
Resolve exceptions without creating another problem
- Late payment: check the actual receipt and apply the agreed expiry rule. Expiry does not erase a confirmed output.
- Underpayment: reconcile the original amount before asking for a top-up, and keep both transfers in the same invoice record.
- Overpayment or refund: agree whether the return is denominated in LTC or fiat and authenticate fresh receiving instructions. A transaction input address does not reliably identify the customer's refund destination.
- MWEB: confirm that the recipient, wallet, conversion route and accounting process support the intended path. Privacy features do not replace the evidence needed for your business records.
Frequently asked questions
Do I have to keep the Litecoin after a client pays?
No. Receiving a payment and choosing to hold LTC are separate decisions. Any conversion still has execution, and withdrawal conditions.
Does the sender's network fee automatically reduce my invoice receipt?
No. Check the actual recipient output. A fee paid on top is separate; subtracting a fee from the requested recipient amount can instead cause an underpayment.
Is tax relevant only when I withdraw money to my bank?
Do not assume that. The US IRS treatment cited above includes service income on receipt and a separate later-disposal calculation. Identify your own jurisdiction and accounting rules rather than treating the bank withdrawal as the only event.
