Thank you. I will look into using that module instead. I'm not sure it will do what I need it to, but I will play with it first before making a determination.

Unfortunately, I don't think the module will work. I need the output to look something like:

<?xml version="1.0" standalone="no"?>
<!DOCTYPE QBXML PUBLIC '-//INTUIT//DTD QBXML QBD 1.1//EN'>
<QBXML>
  <QBXMLMsgsRq onError="stopOnError">
    <TimeTrackingAddRq requestID="1">
      <TimeTrackingAdd>
        <TxnDate>2003-01-01</TxnDate>
        <EntityRef>
          <ListID>40000-1022206382</ListID>
        </EntityRef>
        <CustomerRef>
          <FullName>Cahoots Sports Bar &amp; Grill</FullName>
        </CustomerRef>
        <ItemServiceRef>
          <FullName>AR</FullName>
        </ItemServiceRef>
        <Duration>PT00H01M</Duration>
      </TimeTrackingAdd>
    </TimeTrackingAddRq>
  </QBXMLMsgsRq>
</QBXML>
[download]

For each line, a separate XML needs to be sent to QB because QB is a little quirky with their errors, even if I change "stopOnError" to "continueOnError". I also need to do things with the data before it goes to XML (the Duration and Date are formatted from something else to what you see in the data)

The module you recommended produces something like:

<records>
    <record>
        <Customer>Cahoots Sports Bar &amp; Grill</Customer>
        <Service>AP</Service>
        <Duration>PT00H01M</Duration>
        <Date>2003-01-01</Date>
    </record>
    <record>
        <Customer>Cahoots Sports Bar &amp; Grill</Customer>
        <Service>AP</Service>
        <Duration>PT00H01M</Duration>
        <Date>2003-01-01</Date>
    </record>
    <record>
        <Customer>Cahoots Sports Bar &amp; Grill</Customer>
        <Service>AR</Service>
        <Duration>PT00H01M</Duration>
        <Date>2003-01-01</Date>
    </record>
</records>
[download]

And I'm a little confused by the documentation. But I will keep trying with this module anyway. I'm sure I'm missing some kind of customization point or hack to make it work the way I need it to.