[No QA] Update import instructions and FAQ for company cards

[stephanieelliott]

Added note about downloading the CSV template for company card transaction imports and clarified file upload requirements in the FAQ section.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://8ae7fa9d.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/connect-credit-cards/Import-Company-Card-Transactions-From-a-Spreadsheet

[github-actions]

Link formatting violation: Per Section 7 (Link Formatting), use relative links only and do not use full URLs. This FAQ answer embeds the same full external S3 URL again. Consolidate to a single reference and use a relative/approved link rather than a raw external URL.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes targeted edits to Import-Company-Card-Transactions-From-a-Spreadsheet.md. It adds a prerequisite note about enabling Company Cards in the "Who can..." section, replaces the original enablement Note with a CSV template reference, and adds one new FAQ entry covering upload failures. The changes are small, on-topic, and reinforce the single workflow (importing company card transactions from a spreadsheet). They are helpful additions, but a few governance details need attention.

Scores Summary

• Readability: 8/10 - New sentences are clear, action-oriented, and scannable. The CSV template note and the new FAQ improve user guidance. Minor redundancy exists between the new prerequisite sentence and existing content.
• AI Readiness: 8/10 - The new FAQ heading is a proper question ("What should I do if my file upload fails or results in an error?"), matching real search intent, and feature names match the UI. Metadata is untouched and remains compliant. No new headings break the hierarchy.
• Style Compliance: 6/10 - UI labels are correctly bolded (Company Cards, More features). However, the new content introduces full external URLs (3 instances), and uses a curly apostrophe in "Expensify's", which deviates from the deterministic, exact-text style.

Key Findings

• Positive: The new FAQ is well-formed (question-based heading, direct answer) and complies with FAQ structure rules.
• Positive: The CSV template link is placed inside an explanatory Note rather than within numbered steps, consistent with the link-placement rules.
• Issue: Three full URLs (the S3 CSV template links) are added. The authoring guidelines state "Use relative links only. Do not use full URLs." These are external asset links rather than internal articles, but the rule is stated absolutely - flag for reviewer confirmation that external asset links are acceptable here.
• Issue: The replaced Note removed the original enablement guidance from the steps section. That information is now only in the "Who can..." section. This is acceptable (avoids duplication) but verify the relocation was intentional.
• Minor: "Expensify's" uses a curly apostrophe; prefer a straight apostrophe for consistency with the deterministic writing rule.

Recommendations

• Confirm whether full external (S3) URLs are permitted; if internal hosting/relative linking is expected, convert accordingly.
• Replace the curly apostrophe in "Expensify's" with a straight apostrophe.
• Consider tightening the new prerequisite sentence in the "Who can..." section to avoid overlap with the navigation phrasing already implied elsewhere.

Files Reviewed

• docs/articles/new-expensify/connect-credit-cards/Import-Company-Card-Transactions-From-a-Spreadsheet.md - Minor additions; mostly compliant, with style/link notes above.

Note: Detailed line-by-line feedback has been provided as inline comments.

[melvin-bot]

Concierge reviewer checklist:

• I have verified the accuracy of the article
  • The article is within a hub that makes sense, and the navigation is correct
  • All processes, screenshots, and examples align with current product behavior.
  • All links within the doc have been verified for correct destination and functionality.
• I have verified the readability of the article
  • The article's language is clear, concise, and free of jargon.
  • The grammar, spelling, and punctuation are correct.
  • The article contains at least one image, or that an image is not necessary
• I have verified the formatting of the article
  • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
  • The article has proper text spacing and breaks for readability.
• I have verified the article has the appropriate tone and style
  • The article's tone is professional, friendly, and suitable for the target audience.
  • The article's tone, terminology, and voice are consistent throughout.
• I have verified the overall quality of the article
  • The article is not missing any information, nor does it contain redundant information.
  • The article fully addresses user needs.
• I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @lydiabarclay

[melvin-bot]

@lydiabarclay Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.4.29-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.4.31-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[OSBotify]

🚀 Deployed to production by https://github.com/grgia in version: 9.4.31-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android