Clarify supplier registration in staging#481
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Mexico SAT documentation to clarify that supplier registration is required in non-live environments and how to handle test CSDs when working in sandbox.
Changes:
- Update coverage accordion wording for sandbox CSD usage.
- Update MX SAT issuing guide sandbox vs live supplier requirements and revise the registration note to reflect current sandbox behavior.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| snippets/coverage/mx/accordion.mdx | Adjusts the sandbox environment capability description in the Mexico coverage accordion. |
| guides/mx-sat-issuing.mdx | Clarifies sandbox supplier registration requirements and how to use SW Sapien test CSDs in the issuing guide. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
184
to
+187
| Each CSD is tied to an RFC. When you submit an e-invoice, including the supplier's RFC, SW Sapiens checks for a valid CSD linked to it, as SAT requires a valid certificate to issue invoices. | ||
|
|
||
| <Note> | ||
| To speed things up, we've pre-registered all the test CSDs listed on the [SW Sapien test page](https://developers.sw.com.mx/knowledge-base/donde-encuentro-csd-de-pruebas-vigentes/) in the sandbox. | ||
|
|
||
| If you're working in **sandbox**, you can either: | ||
| - Skip this section and go straight to [Send an Invoice](#send-an-invoice) using a test RFC, or | ||
| - Register your own certificate by following the steps below. | ||
| Registration is required even in the **sandbox** now. When following the steps below in that environment, you don't need a real CSD: you can register either your own company and certificate, or any of the test companies published on the [SW Sapien test page](https://developers.sw.com.mx/knowledge-base/donde-encuentro-csd-de-pruebas-vigentes/), where you can download each test company's certificate, private key, and password. Either way, make sure the supplier's name and RFC matches its certificate. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of APP-638