Establishing secure connection…Loading editor…Preparing document…

Miscellaneous Shell Card

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

MISCELLANEOUS SHELL CARD AGREEMENT

This Miscellaneous Shell Card Agreement ("Agreement") is entered into as of Effective Date: by and between Issuer Name: and Client Name: .

RECITALS

WHEREAS, Issuer is in the business of issuing and managing fuel procurement cards and related account services for commercial fleets and business purchasers; and

WHEREAS, Client desires to obtain one or more Shell-branded procurement cards (each a "Card") for use by authorized employees or agents to purchase fuel, lubricants and other permitted goods and services in accordance with the terms set forth herein.

WHEREAS, Issuer and Client agree to memorialize the rights and obligations of each party with respect to issuance, use, billing and termination of the Card(s).

SCOPE OF WORK

Issuer shall issue Card(s) to Client for the permitted use described below. Issuer will provide account setup, card production, customer support for merchant disputes, monthly billing statements, and online access to transaction data where available. Client shall comply with the Card use policy set forth herein and in any attachments.

PAYMENT TERMS

Client agrees to pay fees and charges in accordance with the schedule below. All amounts are payable in United States dollars unless otherwise agreed in writing.

If payment is not received by the due date, Client will incur a late fee equal to per month or the maximum allowed by law, whichever is less, subject to a minimum late fee of .

TERM AND TERMINATION

This Agreement commences on Start Date: and, unless earlier terminated in accordance with this Agreement, will continue until End Date: .

Either party may terminate this Agreement for convenience upon written notice to the other party at least days prior to the effective termination date. Issuer may suspend or terminate Card privileges immediately upon notice for suspected misuse, breach, nonpayment, or fraudulent activity.

CONFIDENTIALITY

Each party shall keep confidential all non-public information disclosed by the other party in connection with this Agreement, including transaction data and cardholder information, and shall not disclose such information except to the extent reasonably necessary to perform its obligations or as required by law. Confidentiality obligations shall continue for years after termination.

ADDITIONAL TERMS

Client is responsible for all charges incurred on issued Card(s) by authorized cardholders. Client shall maintain adequate procedures to prevent unauthorized use, shall promptly report lost or stolen cards, and shall cooperate with Issuer in investigations. Issuer may audit Client's use of the Card and require verification of receipts. Client shall indemnify and hold Issuer harmless from claims arising from Client's negligence, unauthorized purchases, or failure to collect required taxes.

Limitation of Liability: Except for gross negligence or willful misconduct, neither party shall be liable for incidental, consequential, or punitive damages arising from this Agreement. Issuer's aggregate liability for direct damages shall not exceed the total fees paid by Client in the preceding twelve-month period.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to conflict of laws principles.

ENTIRE AGREEMENT

This Agreement, together with any schedules, attachments, or addenda executed by the parties, constitutes the entire agreement between Issuer and Client with respect to the subject matter hereof and supersedes all prior understandings, proposals, and representations, whether written or oral. Any modification must be in writing and signed by authorized representatives of both parties.

By checking the box and signing below, Client and Issuer acknowledge they have read, understood, and agree to be bound by the terms of this Agreement.

I acknowledge and accept the terms of this Agreement

Issuer:

By:

Date:

Client:

By:

Date:

Enter text✕

What the Miscellaneous Shell Card Is and when it’s used

A Miscellaneous Shell Card is a standardized payment or transaction record used to capture incidental charges, one-off vendor payments, or pooled expense entries when a dedicated payment instrument or specific purchase order is unavailable. The form groups basic merchant data, cardholder or requester details, transaction amount and date, accounting codes, and an approver signature block. Organizations use it to ensure consistent documentation of ad hoc spend, enable timely reconciliation, and create an audit trail for internal controls, tax reporting, and month-end closing.

Why a clear Miscellaneous Shell Card matters

A complete shell card reduces reconciliation time, clarifies who authorized incidental costs, and preserves supporting data needed for tax reporting and internal audits. Properly completed cards support traceability, reduce payment disputes, and help enforce spend policies without requiring bespoke purchase orders for minor transactions.

Why a clear Miscellaneous Shell Card matters

Typical users and contributors

Teams that frequently handle small, irregular purchases or reimbursements rely on a Miscellaneous Shell Card to standardize records before accounting entry.

  • Procurement and purchasing staff who document unscheduled vendor charges for later matching and coding.
  • Accounts payable teams reconciling receipts and routing items for payment and ledger posting.
  • Travel and facilities coordinators capturing incidental expenses where a corporate card is not used.

Clear role delineation speeds processing and ensures the card links each transaction to an accountable approver for audit purposes.

Essential elements to include on a professional card

Design the card so it captures authorization, merchant context, and bookkeeping data in a single glance to support fast approvals and reliable accounting.

Cardholder

Name, department, and contact details for the person responsible for the expense and who can answer follow-up questions during reconciliation.

Merchant

Merchant name, merchant category or service description, and any invoice or receipt reference used to verify goods or services received.

Transaction Limits

Single-transaction limit and monthly aggregate thresholds to indicate whether the charge requires higher-level approval before payment.

Approval Workflow

Designated approver name, role, and signature or e-sign field; include conditional fields for manager escalation when amounts exceed thresholds.

Accounting Codes

General ledger account, cost center, project or PO number fields to allow direct posting and reduce manual reclassification by AP teams.

Audit Trail

Space for date, time, receipt attachment note, and internal reference ID so reviewers can trace activity during internal controls testing.

Security and compliance controls to require

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Audit Logging: Tamper-evident timestamps and action history
HIPAA: BAA required for PHI-containing workflows
21 CFR Part 11: Compliant options for FDA records
SOC 2: SOC 2 Type II attestation available
Accessibility: WCAG 2.0 Level AA support

Principal risks of incomplete or incorrect cards

Tax Penalties: IRC §6721 penalties may apply for incorrect information returns
Backup Withholding: Incorrect TINs can trigger 24% backup withholding
Delayed Reimbursement: Missing approver data causes payment holds
Lost Audit Trail: Handwritten or unlinked receipts impede audits
HIPAA Exposure: Unsecured PHI exposures risk HIPAA violations
Fraud Risk: Unclear authorizations increase misuse potential

Common preparation mistakes to avoid

  • Omitting the approver signature or electronic approval step, which prevents timely payment and weakens internal control evidence.
  • Failing to attach a receipt or invoice reference, causing reconciliation delays and increased AP research time.
  • Using vague descriptions like 'miscellaneous' without vendor or service details, which obstructs cost allocation and audit review.
  • Entering incorrect GL codes or project IDs, leading to misposted expenses and extra month-end journal corrections.

Step-by-step: completing a Miscellaneous Shell Card

Follow these sequential steps to ensure each carded transaction is approved, coded, and archived for accounting and audit purposes.

  • 01
    Capture Details: Enter merchant, invoice number, date, and amount.
  • 02
    Assign Codes: Provide GL account, cost center, and project ID.
  • 03
    Obtain Approval: Collect manager signature or e-approval per limits.
  • 04
    Attach Receipt: Upload or attach a receipt and note payment method.

Typical lifecycle from request to reconciliation

A clear process reduces exceptions and speeds month-end closing; these four stages reflect a common operational flow.

  • Issue or Request: Requester completes the card or submits a ticket for ad hoc purchases.
  • Transaction Capture: Payment occurs and transaction details are uploaded or transcribed onto the card.
  • Review and Approve: Approver verifies the charge, codes it, and signs electronically or on paper.
  • Reconcile: AP matches bank or card statements to the card and posts entries in the ledger.

Digital capabilities that improve accuracy

Digital forms reduce manual errors and integrate with accounting systems to shorten reconciliation and preserve an auditable history.

Fillable Form

Use a structured PDF or web form with required fields and validation to prevent incomplete submissions and guide users through necessary information.

Conditional Fields

Show or hide fields based on amount thresholds or merchant type so approvers see only pertinent details and escalation logic is enforced.

Export Formats

Provide CSV, Excel, and PDF exports to enable direct import into ERP or GL systems and archived signed PDFs for audits.

Integrations

Connect to accounting and storage platforms such as Salesforce, NetSuite, Microsoft 365, Google Workspace, Box, and Procore for automated routing.

Practical tips for accurate and efficient completion

Adopt guardrails and automation to reduce exceptions and keep reconciliation timelines predictable.

Standardize field entries
Use controlled lists for merchants, GL codes, and cost centers to ensure consistent posting and reduce manual lookups during month-end reconciliation.
Set approval thresholds
Define clear dollar thresholds that trigger additional approver levels and require receipt attachments for amounts above specified limits.
Require receipts
Mandate receipt or invoice uploads with every submission and verify legibility to prevent disputes and facilitate audit sampling.
Schedule reconciliations
Perform regular reconciliations—weekly or monthly depending on volume—to catch errors early and avoid large backlog adjustments.

Typical timing expectations and submission deadlines

Define deadlines to control processing windows and align card entries with accounting cutoffs and tax reporting cycles.

Submission Window:

Submit card within 30 days of transaction to allow timely matching and payment.

Monthly Reconciliation:

Close reconciliations within five business days after month end to maintain accurate ledgers.

Tax Records:

Retain transaction support for at least 3 years to satisfy IRS recordkeeping (IRC §6501(a)).

I-9 / Employment:

If tied to hiring, follow I-9 retention: 3 years after hire or 1 year after termination, whichever is later.

HIPAA-linked Records:

Healthcare-related documentation must be retained 6 years per 45 CFR §164.530(j).

FAQs and troubleshooting for common issues

Answers to frequent questions about validity, attachments, signatures, and troubleshooting when card submissions fail validation or are rejected by accounting.


Need help? Contact support

Vendor pricing and feature snapshot for e-signature and processing

Below is a concise comparison of starting price, trial availability, bulk send, audit trail, HIPAA support, and envelope cap; signNow is shown first for parity with internal references.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial, no credit card required Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Available (Business Premium tier) Available Available Available Varies by plan
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA required) Varies by plan Varies by plan No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan
be ready to get more
Join over 28 million airSlate SignNow users